From: Clemens Fischer <ino@despammed.com>
Subject: Re: gnus-simplify-subject-fuzzy doesn't work
Date: Sat, 12 Oct 2002 15:58:36 +0200 [thread overview]
Message-ID: <it07oj1v.fsf@ID-23066.news.dfncis.de> (raw)
In-Reply-To: <87hefsddcm.fsf@enberg.org>
Henrik Enberg <henrik@enberg.org>:
>> with "\\[despammed\\] ". i want to get rid of this string, because i
>
> If you want to hide it from the summary view, you should use
> `gnus-list-identifiers'.
yes, thanks to you and ted for this tip. it works, although i do not
only want to hide it from the summary, but from replies as well.
also, i don't understand why g-simplify-subject-fuzzy doesn't do
that. i can't even see any irregularities in the source.
clemens
next prev parent reply other threads:[~2002-10-12 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 18:27 clemens fischer
2002-10-11 18:44 ` Henrik Enberg
2002-10-12 13:58 ` Clemens Fischer [this message]
2002-10-12 19:22 ` Josh Huber
2002-10-13 14:15 ` Clemens Fischer
2002-10-16 11:44 ` Niklas Morberg
2002-10-16 20:02 ` clemens fischer
2002-10-17 6:48 ` Niklas Morberg
2002-10-13 17:28 ` Kai Großjohann
2002-10-17 6:55 ` Niklas Morberg
2002-10-17 8:26 ` Simon Josefsson
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=it07oj1v.fsf@ID-23066.news.dfncis.de \
--to=ino@despammed.com \
/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).