From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: 'nother split-fancy question
Date: Mon, 10 Mar 2008 21:40:30 +0100 [thread overview]
Message-ID: <v9pru2s475.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2iqzuvehj.fsf@nwalsh.com>
On Mon, Mar 10 2008, Norman Walsh wrote:
> Consider the following headers:
[...]
> To: Carbon Emacs <carbon-emacs@googlegroups.com>
[...]
> Can anyone explain why this rule:
>
> (to "carbon-emacs@googlegroups\\.com" "googlegroups.carbon-emacs")
>
> matches and works fine, but this rule:
>
> (to "\\(.*\\)@googlegroups\\.com" "googlegroups.\\1")
>
> sends the message to "googlegroups." ?
Does "\\([a-z0-9_-]+\\)@googlegroups\\.com" work?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-03-10 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 14:30 Norman Walsh
2008-03-10 20:40 ` Reiner Steib [this message]
2008-03-13 10:52 ` Johan Bockgård
2008-03-11 16:16 ` Ted Zlatanov
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=v9pru2s475.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).