Definitely a known issue. No easy way to fix it without someone doing
a deep pass on syntax propertization I think. I have a version of
rainbow delimiters mode that tries to work around this at least for
font locking, but it is severely broken and has some nasty quadratic
performance issues in
I think this is a known problem (Org probably needs a PROBLEMS or
KNOWN_PROBLEMS file in addition to a NEWS file).
Problem is that org treats things like <> as special paren syntax
because they are used by org. Unfortunately, this causes problems with
things like paren matching in org files if
Inside org-babel code blocks, emacs matches parens incorrectly whenever
different bracket types (eg <> {} []) are used.
For example the following in an .org file will cause check-parens to throw
an error:
#+BEGIN_SRC emacs-lisp
(> 1 0)
#+END_SRC
Where in an .el it will interpret the parens
