On Thu, 21 Feb 2002 13:35:25 +0900, "Stephen J. Turnbull"
<stephen(a)xemacs.org> said:
I'm probably unusual; I do tend to have buffer-specific usage of
font-lock (I turn it on when I'm worried about hairy syntax errors,
otherwise off when I think I know what I'm doing). So I agree with
Odd - most of *my* hairy syntax errors are things that font-lock
will pass, because they don't become errors until you've done
a 'gcc -E'. In fact, I seem to remember that a *lot* of font-lock
and lazy-lock and related fontification issues have been caused by
the fact that in general, their opinion of the syntax is based on a
much narrower view than the compiler's (for instance, it will pass
something as legal because it *looks* legal based on what's within
100 lines either side of 'point' - but in fact it's broken because of
a ' instead of a ", or a missing semicolon 2,394 lines back ;)
/Valdis (who wishes I didn't get an 'unmatched parenthesis' and a
bright-red overlay from 'point' back to a '{' in my X-Face header when
I type a ;) (And yes, I know it's probably customizable, I just haven't
dug into how to do it the way I want it...)