From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: [PATCH] Fix gnus-message-citation-mode for (S)XEmacs
Date: Tue, 13 Feb 2007 14:49:25 -0500 [thread overview]
Message-ID: <m1ps8dg7ne.fsf@davestoy.homelinux.org> (raw)
In-Reply-To: <b4m64a6tecu.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue\, 13 Feb 2007 21\:46\:09 +0900")
>>>>> On Tue, 13 Feb 2007 21:46:09 +0900, Katsumi Yamaoka <yamaoka@jpl.org> said:
>>>>>>> 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?
It's odd. When working on my linux machine at home I get the same messages:
Fontifying *wide reply to Katsumi Yamaoka on ding@gnus.org*...
Fontifying *wide reply to Katsumi Yamaoka on ding@gnus.org*... done.
Fontifying mail to ding@gnus.org...
Fontifying mail to ding@gnus.org... (regexps)....
Fontifying mail to ding@gnus.org... (regexps)........
Fontifying mail to ding@gnus.org... (regexps)........
Fontifying mail to ding@gnus.org... (regexps).........
Fontifying mail to ding@gnus.org... (regexps)..........
Fontifying mail to ding@gnus.org... (regexps).............
Fontifying mail to ding@gnus.org... (regexps)..............
Fontifying mail to ding@gnus.org... (regexps)...............
Fontifying mail to ding@gnus.org... (regexps)...............
Fontifying mail to ding@gnus.org... (regexps)...............
Fontifying mail to ding@gnus.org... (regexps)...............
Fontifying mail to ding@gnus.org... (regexps)...............
Fontifying mail to ding@gnus.org... (regexps)................
Fontifying mail to ding@gnus.org... aborted.aborted.
I don't see them at all when using my machine at work, which is
running Windows XP with XEmacs under cygwin (locally compiled). I use
the same .xemacs/init.el, .xemacs/custom.el and .gnus on both
machines. I cannot explain the difference. However, the message
buffers look equivalent with fontified headers and included text
(though it's all one color whereas it sounds like this change is
supposed to make included text look nicer).
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2007-02-13 19:49 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
2007-02-13 19:49 ` Dave Goldberg [this message]
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=m1ps8dg7ne.fsf@davestoy.homelinux.org \
--to=david.goldberg6@verizon.net \
--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).