From: Steinar Bang <sb@metis.no>
Subject: Re: Replacing "AW:" with "Re:"
Date: 17 Sep 1999 09:37:21 +0200 [thread overview]
Message-ID: <wh9066yoni.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Lars Balker Rasmussen's message of "Thu, 16 Sep 1999 19:40:11 GMT"
>>>>> Lars Balker Rasmussen <lbr@image.dk>:
> Steinar Bang <sb@metis.no> writes:
>> (As well as AW, this takes care of "Ad", "SV" and "RE", and the
>> "galloping Re: SV: Re: syndrome...)
>>
>> Unfortunately this doesn't help with USENET messages. :-/
> I found that most of the problem disappeared with the following:
> (setq gnus-simplify-ignored-prefixes "^\\(Sv: \\|Re: \\)+"
> gnus-simplify-subject-functions '(gnus-simplify-subject
> gnus-simplify-whitespace))
> (fill in your favourite Re-variants).
Does this fix subjects in summary listings? Or just in the article
itself?
next prev parent reply other threads:[~1999-09-17 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-16 9:36 Jochen Lillich
1999-09-16 10:39 ` Jens Kloecker
1999-09-16 11:03 ` Steinar Bang
1999-09-16 18:30 ` Robert Bihlmeyer
1999-09-16 19:40 ` Lars Balker Rasmussen
1999-09-17 7:37 ` Steinar Bang [this message]
1999-09-18 9:51 ` Lars Balker Rasmussen
1999-09-20 13:26 ` Jan Rychter
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=wh9066yoni.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).