"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
I doubt it's your settings that are wrong, although of course
something unusual about them may be the trigger. This is probably
internal to some package, or even font-lock itself.
What mode does this happen in? Are there particular files that
usually trigger this while others are warning-free?
It seems that one of the culprit is
lazy-lock-mode
I changed to lazy-shot-mode (which I abandoned a while a ago, for a
reason I already forgot)
I remember a discussing about this mode and the fact that it uses the
C engine, but I forgot the details.
Any ideas?