From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: fancy splitting
Date: Sun, 30 Mar 2003 05:21:56 +0200 [thread overview]
Message-ID: <m3y92xv8rv.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <shbs0876o6.fsf@tux.gnu.franken.de>
Karl Eichwalder <keichwa@gmx.net> writes:
> Documentation on this issue is not that userfriendly; I still cannot
> see how it's possible to do the right thing with mails from lists; the
> dash in names seems to hurt. This does not work:
[...]
> ("List-Post" "mailto:\\b\\(\\w+\\)@.*" "list.\\1")
I think the dashes probably don't have anything to do with it. The
problem is that fancy mail splitting wraps everything in \b ... \b,
which means that @.* will fail.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-03-30 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 20:37 Karl Eichwalder
2003-03-30 3:21 ` Lars Magne Ingebrigtsen [this message]
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=m3y92xv8rv.fsf@quimbies.gnus.org \
--to=larsi@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).