From: Charles Millar <millarc@verizon.net>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Greater than, less than bug in emacs-lisp source block
Date: Thu, 2 Sep 2021 14:10:21 -0400 [thread overview]
Message-ID: <b2a35533-82cd-b585-b1ab-3ca21adcafdf@verizon.net> (raw)
In-Reply-To: b2a35533-82cd-b585-b1ab-3ca21adcafdf.ref@verizon.net
Set up:
GNU Emacs 28.0.50 (build 344, x86_64-pc-linux-gnu, GTK+ Version 3.24.23,
cairo version 1.16.0) of 2020-12-31
Org mode version 9.4.6 (release_9.4.6-637-gd70f28 @
/usr/local/share/org-mode/lisp/)
The following code will evaluate
#+begin_src emacs-lisp
(defun Foo ()
(if (= 2 4) bar))
#+end_src
#+RESULTS:
: Foo
and the opening and closing parentheses match.
If a greater than is inserted instead of equals, thus
#+begin_src emacs-lisp
(defun Foo ()
(if (> 2 4) bar))
#+end_src
it apparently evaluates, however, the closing parenthesis immediately
following the "4" is paired with the opening paren before "if" and not
the opening paren immediately before the ">"
A "less than" results with stranger parenthesis matching - the closing
paren after the "4" matches no others; the closing paren immediately
after "bar" matches the opening paren before "if"
Charlie Millar
next parent reply other threads:[~2021-09-02 18:10 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 ` Charles Millar [this message]
2021-09-02 18:24 ` Greater than, less than bug in emacs-lisp source block John Kitchin
2021-09-02 22:36 ` Arthur Miller
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2a35533-82cd-b585-b1ab-3ca21adcafdf@verizon.net \
--to=millarc@verizon.net \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).