From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: (yet another) problem with nnmail-split-fancy
Date: Wed, 05 Mar 2003 21:25:51 +0100 [thread overview]
Message-ID: <84smu11rxs.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <uzno9fvsm.fsf@ni.com>
Peter Ilberg <peter.ilberg@ni.com> writes:
> The following is taken directly from the Gnus manual entry on
> "Fancy Mail Splitting" (near the bottom):
>
> If you want to have Gnus create groups dynamically based on some
> information in the headers (i.e., do `replace-match'-like substitutions
> in the group names), you can say things like:
>
> (any "debian-\\b\\(\\w+\\)@lists.debian.org" "mail.debian.\\1")
In this case, the preceding "debian-" string makes sure that the \\w+
matches enough chars.
--
A preposition is not a good thing to end a sentence with.
next parent reply other threads:[~2003-03-05 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ygdzno9dd7j.fsf@legolas.retis>
[not found] ` <84el5llnrv.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <uzno9fvsm.fsf@ni.com>
2003-03-05 20:25 ` Kai Großjohann [this message]
[not found] ` <uisuxft2k.fsf@ni.com>
2003-03-07 12:29 ` Kai Großjohann
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=84smu11rxs.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).