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

2021-04-03 Thread Arthur Miller
John Kitchin writes: > 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 wo

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

2021-04-02 Thread Tom Gillespie
Reposting my reply to the emacs-devel thread here as well. The hack I mention that has performance issues was derived from John's solution for the <> issue (though the performance issues are all of my own creation). Best, Tom This is a known issue with org babel blocks. It is due to the fact that

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

2021-04-02 Thread John Kitchin
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. John ---

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

2021-04-01 Thread Tim Cross
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 wrote: > > Is it me or is it a bug? > > When in org mode in an elisp block, this seems to confuse syntax > checker: > > #+begin_src emacs-lisp > (pr