From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: Using gnus-list-identifiers
Date: 16 Sep 1999 10:09:11 +0200 [thread overview]
Message-ID: <iluemfz46s8.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: "Rene H. Larsen"'s message of "16 Sep 1999 01:58:06 +0200"
Rene H. Larsen <renehl@post1.tele.dk> writes:
> This makes list identifier hiding *a lot* less useful than it could
> be. I don't like having some catch-all regexp applied to the subject
> of all the articles that I read. Instead, I'd like to be able to
> specify exactly the right regexp on just the groups that need it.
What about using list of regexp's? I use
(setq gnus-list-identifiers '("\\[zebra [0-9]+\\]" "\\[gtk-list\\]"
"LAM:" "linux-ipsec:" "DENTS:"
"\\[linux-security\\]" "FVWM:"))
I think the removal of list identifiers are done before summary local
variables are bound.
next prev parent reply other threads:[~1999-09-16 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-15 23:58 Rene H. Larsen
1999-09-16 0:53 ` Karl Kleinpaste
1999-09-16 1:41 ` Rene H. Larsen
1999-09-16 2:09 ` Karl Kleinpaste
1999-09-16 11:20 ` Rene H. Larsen
1999-09-16 8:09 ` Simon Josefsson [this message]
1999-09-16 11:23 ` Rene H. Larsen
1999-09-17 14:01 ` Per Abrahamsen
1999-09-17 17:28 ` Rene H. Larsen
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=iluemfz46s8.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--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).