Hi Lawrence,
Lawrence Bottorff <borg...@gmail.com> writes: > Not sure what you mean. This is the problem, i.e., just this code > > #+begin_src emacs-lisp > (> 1 2) > #+end_src > > in an org file produces a parens mismatch, which, BTW, check-parens also > flags. Anywhere else (e.g., *scratch*) in Emacs this code produces no > mismatch. > In an org buffer, '>' is a closing delimiter. In an elisp buffer (like the *scratch* one), '>' is just a symbol (you can use the command 'describe-char' to have a description of the character at point). In short, if I understand correctly, it's not supposed to work like you expect; you need to edit the source block to do things that really depend on the code source syntax (C-c '). Bruno > On Thu, May 2, 2019 at 10:35 AM Berry, Charles <ccbe...@ucsd.edu> wrote: > >> >> >> > On May 1, 2019, at 7:56 PM, Lawrence Bottorff <borg...@gmail.com> wrote: >> > >> > Wondering if you have seen this over at emacs.stackexchange. Very >> puzzling why the parens mismatch in a babel emacs-lisp block, but not >> anywhere else in Emacs. >> >> I don't know the details but this ECM might help: >> >> #+begin_src emacs-lisp >> (> 1 2) >> #+end_src >> >> The right broken bracket matches the left parenthesis in org-mode, but not >> in a Lisp Interaction Mode buffer. >> >> HTH >> >> Chuck >>