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

[Arthur Miller <arthur.miller@live.com>]

Tom Gillespie <tgbugs@gmail.com> writes:

> This is a known issue with org babel blocks. It is due to the fact
> that org babel translates the font locking for the language but not
> the syntax propertization. Another frequent cause is the bash case
> statement. The end result is that unmatched parens leak out from the
> babel blocks and wreak havoc elsewhere in the org file unless you
> balance out the parens e.g. in a comment. I have a hacked fix for
> this, but it has horrible performance, especially with line numbers
> enabled. I think that a proper solution would run arbitrary syntax
> propertization on subsets of a buffer without having to continually
> check where those subsets start or end. Best,
> Tom

Thanks for the explanation!

I don't know how org-babel works, I guess it opens another buffer,
font-locks syntax there and copy it over? What was the reason why they
don't copy other properties? Performance or something else?