Re: message mode loses highlighting

[Katsumi Yamaoka <yamaoka@jpl.org>]

Hi,

>>>>> In <4nbrw62ykx.fsf@lockgroove.bwh.harvard.edu>
>>>>>	Ted Zlatanov <tzz@lifelogs.com> wrote:

> This is my current function:

> (defun tzz-highlighting-install ()
[...]

I'm well aware of that.  How did you use to turn on font-lock in
a messege buffer (before using it)?  AFAIK, Gnus doesn't turn on
font-lock for the message-mode by default, except for XEmacs.
So, I'm using the following code:

(cond ((featurep 'xemacs)
       )
      (t
       (add-hook 'message-mode-hook 'turn-on-font-lock)))

If the tzz-highlighting-install function is only the way to turn
on font-lock for the message-mode (by way of the text-mode), the
value of the message-font-lock-keywords variable will never be
regarded.  It was mentioned in my last message as follows:

>> font-lock is first turned on for the text-mode and only keywords
>> for the text-mode are used.

> According to the docs, font-lock-mode works the same with the t and
> the 1 parameters, so what you suggest shouldn't make a difference.

You are right.  The tzz- function will surely turn on font-lock
for the *text-mode* and it will be still turned on for the
message-mode.  Even so, the message-font-lock-keywords variable
will still be ignored.  What you should do is to add the
following hook in order to turn on font-lock again for the
*message-mode*.  For that purpose, it is necessary to use
`(font-lock-mode 1)' rather than `turn-on-font-lock' since
t-o-f-l does nothing if font-lock is already turned on:

(add-hook 'message-mode-hook (lambda nil (font-lock-mode 1)))

P.S.
Sorry for my funny English.  I am a sophisticated writer in
Japanese, but not in English. ;-)
-- 
Katsumi Yamaoka <yamaoka@jpl.org>