From:
[email protected]
This bug has been fixed as of xemacs21-basesupport version
2002.03.29-1. This bug can be closed.
I have tested this with starting xemacs with the -q option and then
manually turning on font lock on a C++ buffer. It also works with my
own customized cc-mode configuration when invoking ~/.emacs.
$ dpkg -l 'xemacs21*' | grep ^[hi]
ii xemacs21 21.4.6-8 Editor and kitchen sink
hi xemacs21-bases 2002.03.29-1 Editor and kitchen sink -- compiled elisp su hi xemacs21-bases 2002.03.29-1 Editor and kitchen sink -- source elisp supp ii xemacs21-bin 21.4.6-8 Editor and kitchen sink -- support binaries ii xemacs21-nomul 21.4.6-8 Editor and kitchen sink -- Non-mule binary
ii xemacs21-suppo 21.4.6-8 Editor and kitchen sink -- architecture inde ii xemacs21-suppo 21.4.6-8 Editor and kitchen sink -- non-required libr
<details>
The bug does not actually apply to cc-mode. C++ keywords are actually
defined in font-lock.el and not in cc-mode. The "typename" keyword is
only highlighted when "medium" level (level 2) or higher fontification is enabled. Examining the definition of c++-font-lock-keywords-2 in
font-lock.el will make it clear that "typename" is included (it is
defined in the c++-type-types regex in the enclosing let statement).
It is even possible that the person who reported this bug was unaware
of the use of font-lock-maximum-decoration (font-lock.el seems to have
been last updated in 2001 acccording to copyright statements).Or maybe
it really was a bug at that time even with maximum decoration. I don't
know.
In any case, the default xemacs21 installation now sets font-lock-maximum-decoration to 't' and so "typename" is highlighted
by default
</details>
Cheers!
Shyamal
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)