Christoph Wedler <wedler(a)fmi.uni-passau.de> writes:
>>>>>"RT" == Raymond Toy
<toy(a)rtp.ericsson.se> writes:
RT> What I would like is some way of adding additional items to the
RT> font-lock-keywords. Why? I want to have file-local entries like
RT> typedefs that get font-locked appropriately. You know, things like
RT> size_t, ptr_diff_t, and whatever other type I might have should get
RT> highlighted.
FSFmacs-20.2's font-lock has `c-font-lock-extra-types' (same for C++).
Use the corresponding entries with the form (eval . FORM), see
`font-lock-keywords'.
RT> I supposed I could just append the new patterns to
RT> font-lock-keywords, but that requires eval in the file-local
RT> variables section. Uncool, perhaps.
If there is such a variable, it should be a 'risky-local-variable since
you can include any code.
RT> Maybe a buffer-local variable, say, font-lock-local, that contains
RT> additional patterns to be matched. Would probably need to modify
RT> font-lock a bit so that it knows about this variable.
The concept of `font-lock-fontify-region-function' in FSFmacs-20.2 is
more general.
Based on this comment and the comment of others, it seems that
FSFmacs-20.2 has what I want.
Unfortunately, as soon as XEmacs had tty support, I blew away my copy
of FSFmacs and never looked back.... Well, except for OS/2 and now
NT, but NT will have XEmacs, so I'm going to blow away emacs there
too. Just need an OS/2 version now (doable with the XFree86 OS/2?).
:-)
Ray