From: Arthur Miller <arthur.miller@live.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Charles Millar <millarc@verizon.net>
Subject: Re: Greater than, less than bug in emacs-lisp source block
Date: Fri, 03 Sep 2021 00:36:23 +0200 [thread overview]
Message-ID: <AM9PR09MB49776B81D29DE6AF187704E896CE9@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <CAJ51ETqTg_PuAT5B5CvcYm1VU6yQupgEytpikp2acVwZoG_UsQ@mail.gmail.com> (John Kitchin's message of "Thu, 2 Sep 2021 14:24:58 -0400")
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> I think this issue is described in
> https://emacs.stackexchange.com/questions/50216/org-mode-code-block-parentheses-mismatch. There are also some
> solutions there.
I wasn't able to get that to work in my Emacs. I did something simpler though,
that seems to work for me:
#+begin_src emacs-lisp
(defmacro gt (n1 n2)
`(> ,n1 ,n2))
(defmacro gte (n1 n2)
`(>= ,n1 ,n2))
(defmacro lt (n1 n2)
`(< ,n1 ,n2))
(defmacro lte (n1 n2)
`(<= ,n1 ,n2))
;; example usage
(dolist (s templist)
(while (lt (length s) l)
(setq s (concat s " ")))
(push (concat "[ " s " ]") kwdlist))
#+end_src
next prev parent reply other threads:[~2021-09-02 22:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2a35533-82cd-b585-b1ab-3ca21adcafdf.ref@verizon.net>
2021-09-02 18:10 ` Greater than, less than bug in emacs-lisp source block Charles Millar
2021-09-02 18:24 ` John Kitchin
2021-09-02 22:36 ` Arthur Miller [this message]
2021-09-03 11:14 ` Fwd: " Charles Millar
2021-09-03 11:12 ` Bug " Charles Millar
2021-09-03 12:00 ` John Kitchin
2021-09-03 13:40 ` Tim Cross
2021-09-03 16:02 ` John Kitchin
2021-09-04 21:05 ` Tim Cross
2021-09-05 5:55 ` Arthur Miller
2021-09-05 8:37 ` Tim Cross
2021-09-05 10:34 ` Arthur Miller
2021-09-06 4:29 ` Greg Minshall
2021-09-07 11:31 ` Eric S Fraga
2021-09-07 20:23 ` John Kitchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM9PR09MB49776B81D29DE6AF187704E896CE9@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=millarc@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.