From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: [PATCH] Fix gnus-message-citation-mode for (S)XEmacs
Date: Tue, 13 Feb 2007 21:46:09 +0900 [thread overview]
Message-ID: <b4m64a6tecu.fsf@jpl.org> (raw)
In-Reply-To: <b4mirecp6sb.fsf@jpl.org>
>>>>>> In <m1r6t0mtg9.fsf@davestoy.homelinux.org> Dave Goldberg wrote:
>> but I do appear to be getting at least the same fontification I had
>> before this update.
>>>>> In <b4mirecp6sb.fsf@jpl.org> Katsumi Yamaoka wrote:
> I have the same problem as yours with the home pc.
I seem to have solved this problem. Could you try it?
Formerly `gnus-message-citation-mode' modified the value of
`font-lock-keywords' directly. However, the value is determined
according to the value of `font-lock-defaults' normally and the
variables listed in `font-lock-defaults' don't have the keywords
for `gnus-message-citation-mode'. So, it is possible that
`gnus-message-citation-mode' is invalidated if some program[1]
resets font-lock-keywords' according to `font-lock-defaults' for
some purpose or a user resets it in order to apply the value of
`message-font-lock-keywords' that a user customized using
`gnus-message-setup-hook'[2] for example.
I've made changes to make `gnus-message-citation-mode' work in
the different way. Now `message-font-lock-keywords' is buffer
local in message buffers and gains the elements of
`gnus-message-citation-keywords'. `font-lock-add-keywords' and
`font-lock-remove-keywords' are no longer used.
[1] At least develock.el does it.
[2] Take care not to disregard the values added to
`message-font-lock-keywords' by `gnus-message-citation-mode'
if you do something in `gnus-message-setup-hook'.
Regards,
next prev parent reply other threads:[~2007-02-13 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 7:18 Steve Youngs
2006-12-31 11:52 ` Reiner Steib
2007-01-01 7:26 ` Katsumi Yamaoka
2007-02-07 9:25 ` Katsumi Yamaoka
2007-02-07 15:33 ` Dave Goldberg
2007-02-08 4:42 ` Katsumi Yamaoka
2007-02-08 17:48 ` Dave Goldberg
2007-02-08 23:29 ` Katsumi Yamaoka
2007-02-13 12:46 ` Katsumi Yamaoka [this message]
2007-02-13 19:49 ` Dave Goldberg
2007-02-14 0:29 ` Katsumi Yamaoka
2007-02-28 21:14 ` Dave Goldberg
2007-02-28 22:32 ` Katsumi Yamaoka
2007-03-01 16:29 ` Dave Goldberg
2007-03-02 15:28 ` Dave Goldberg
2007-02-09 23:48 ` Steve Youngs
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=b4m64a6tecu.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).