From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: message mode loses highlighting
Date: Tue, 01 Jul 2003 21:02:30 +0900 [thread overview]
Message-ID: <b9y7k72zc89.fsf@jpl.org> (raw)
In-Reply-To: <4n7k79vzjy.fsf@lockgroove.bwh.harvard.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 905 bytes --]
>>>>> 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.
> I guess I can look at the message mode source. I'm just so busy right
> now that I will probably get to it next year :)
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. :)
Since message-mode is derived from text-mode as Johan Bockg^[.A^[Nerd
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).
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2003-07-01 12:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 15:40 Ted Zlatanov
2003-06-25 23:26 ` Johan Bockgård
2003-06-26 4:42 ` Ted Zlatanov
2003-06-26 5:24 ` Harry Putnam
2003-06-26 11:38 ` Ted Zlatanov
2003-07-01 12:02 ` Katsumi Yamaoka [this message]
2003-07-07 14:36 ` Ted Zlatanov
2003-07-07 16:54 ` Wes Hardaker
2003-07-08 2:34 ` Katsumi Yamaoka
2003-07-10 20:33 ` Ted Zlatanov
2003-07-11 6:50 ` Katsumi Yamaoka
2003-07-11 15:21 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9y7k72zc89.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).