Re: Mysterious fontification/C++ context issue

[martin rudalics]

>>BTW, in Elisp an open bracket in column zero of a string should not
>>confuse Emacs.  Yet you highlight it with `font-lock-warning-face'.
>
>
> Indeed, it *shouldn't*, but it does confuse Emacs, which is why it's
> highlighted ;-(.  We should fix it so it doesn't confuse Emacs any more (and
> doesn't get highlighted either).

Due to the fact that "\\s(" is hardwired in `font-lock-compile-keywords'
and can't be set individually by a major mode.  A minor issue showing
that it's not entirely trivial to give a simple recipe fitting all major
modes.

What I meant is "stay away from putting an open paren in column zero
unless it starts a defun" in any programming mode where "open paren" is
what the syntax table says it is.  It's one constraint for the user,
easy to explain, understand, and implement, difficult to defend, tho.