Re: message mode loses highlighting

[Ted Zlatanov <tzz@lifelogs.com>]

On Tue, 01 Jul 2003, yamaoka@jpl.org wrote:
>>>>>> In <4n7k79vzjy.fsf@lockgroove.bwh.harvard.edu>
>>>>>>	Ted Zlatanov <tzz@lifelogs.com> wrote:
> 
>> What I posted is the only customization involving fontlock I have.
>> In any case, add-keywords should not override any other font
>> locking, according to the docs, that's why I'm puzzled.
> 
> If you use turn-on-font-lock for the message-mode, replace it
> with `(lambda nil (font-lock-mode 1))' and your message buffer
> will revive. :)

This is my current function:

(defun tzz-highlighting-install ()
  (interactive)
  (font-lock-mode t)
  (font-lock-add-keywords
   nil 
   `(("^\\([^-A-Za-z0-9]+\\)$" (0 'font-lock-empty-line-face))
     ("\n" (0 'font-lock-empty-line-face))
     ("\\(FIXME\\|TODO\\)" (1 'font-lock-warning-face prepend)))))

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.

> Since message-mode is derived from text-mode as Johan Bockgård
> said, font-lock is first turned on for the text-mode and only
> keywords for the text-mode are used.  When font-lock has already
> been turned on, even if turn-on-font-lock is performed for the
> message-mode, nothing changes (see font-lock.el).

Hmm, so how can I do what I need to do?

Maybe I can detect message-mode and when it's active, skip execution
of the font-lock machinery above?  It would be better for me, however,
to have the highlighting in message-mode as well.

Thanks for your help
Ted