[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Font lock in org+elisp confused with ?\[

From: John Kitchin
Subject: Re: Font lock in org+elisp confused with ?\[
Date: Fri, 2 Apr 2021 09:03:53 -0400

This is related to the issues with <> in src blocks. [ and ] have open and close syntactical meanings like < and > do in org files. A similar solution as found in https://emacs.stackexchange.com/questions/50216/org-mode-code-block-parentheses-mismatch seems to work to fix it.


Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

On Fri, Apr 2, 2021 at 12:24 AM Tim Cross <theophilusx@gmail.com> wrote:
I'm forwarding this to the emacs-orgmode list as this is something org maintainers probably need to see. 

On Thu, 1 Apr 2021 at 15:43, Arthur Miller <arthur.miller@live.com> wrote:

Is it me or is it a bug?

When in org mode in an elisp block, this seems to confuse syntax

#+begin_src emacs-lisp
  (if (= (following-char) ?\])
      (forward-char -1))

Identation seems to think it is one level extra, and it also shows as
error. Same of course when testing for ?\[.

It does evaluate correctly. Ordinary elisp buffer does not have problem
with this, only when in code blocks in org-mode or elisp mode.I can send
in some screenshot with errors if needed.



Tim Cross

reply via email to

[Prev in Thread] Current Thread [Next in Thread]