From: Steve Youngs <youngs_s@ozlinx.com.au>
Subject: Re: cite fontification not right.
Date: 16 Nov 2000 03:08:26 +1000 [thread overview]
Message-ID: <microsoft_free.81d7fx5fjp.fsf@slackware.mynet.pc> (raw)
In-Reply-To: <87ofzhnpc1.fsf@serafina-pekkala.dme.org>
* "dme" == dme <dme@dme.org> writes:
* youngs_s@ozlinx.com.au [2000-11-15 15:10:45]
>>Is it me/XEmacs, or has something in Gnus broken recently?
dme> I broke this. We have been discussing the issues here - I posted a
dme> patch earlier today which corrected the behaviour, if you could try
dme> it and provide feedback it would be appreciated (the message was
dme> titled `message-cite-prefix-regexp').
I missed that, is this list archived anywhere? Or, alternatively,
could you please send me the patch?
Thanks.
--
|---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---|
| It's a funny thing about life; if you refuse to accept |
| anything but the best, you very often get it |
|-----------------------------<mailto:youngs_s@ozlinx.com.au>---|
next prev parent reply other threads:[~2000-11-15 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 15:10 Steve Youngs
2000-11-15 16:59 ` dme
2000-11-15 17:08 ` Steve Youngs [this message]
2000-11-15 17:47 ` ShengHuo ZHU
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=microsoft_free.81d7fx5fjp.fsf@slackware.mynet.pc \
--to=youngs_s@ozlinx.com.au \
/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).