From: Leonidas Tsampros <ltsampros@upnet.gr>
To: Norman Walsh <ndw@nwalsh.com>
Cc: ding@gnus.org
Subject: Re: Random regex/fancy-split question
Date: Tue, 05 Apr 2011 16:05:53 +0300 [thread overview]
Message-ID: <87y63ox2z2.fsf@bifteki.lan> (raw)
In-Reply-To: <m2ei5hynas.fsf@nwalsh.com> (Norman Walsh's message of "Tue, 05 Apr 2011 07:01:31 -0400")
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
Norman Walsh <ndw@nwalsh.com> writes:
> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>>>>>>> "Norman" == Norman Walsh <ndw@nwalsh.com> writes:
>>
>> Norman> Hello world,
>> Norman> Every now and then I stumble over a new google group for which this
>> Norman> fancy split line doesn't work:
>>
>> Norman> (to "\\(.+\\)@googlegroups\\.com" "googlegroups.\\1")
>>
>> Maybe the .+ which is matching the longest match here:
>>
>> Norman> To: "epub-working-group@googlegroups.com"
>> Norman> <epub-working-group@googlegroups.com>
>>
>> which would be:
>>
>> epub-working-group@googlegroups.com" <epub-working-group
>>
>> is trying to make a group called
>>
>> googlegroups.epub-working-group@googlegroups.com" <epub-working-group
>>
>> which GNUS should reasonably reject?
>
> Maybe. But how does that become "googlegroups."? Ah well. I guess if I really
> get tired of adding the one-off rules, I can always go read the source :-)
>
> Be seeing you,
> norm
I'm pretty sure I had stumbled upon the same problem. For googlegroups I
can see that I have defined those rules here, so it's pretty certain:
("sender" "django-users@googlegroups.com" "mail.gg.django-users")
("sender" "django-developers@googlegroups.com" "mail.gg.django-developers")
("sender" "django-announce@googlegroups.com" "mail.gg.django-announce")
("list-id" ".*<\\(.+\\)\\.googlegroups\\.com>.*" "mail.gg.\\1")
However, I ran the last regexp in re-builder, and it seems to match
'epub-working-group' in from the angled portion of the To:
address. Also, in my setup, I removed the first 3 django specific
entries, and again B t reported a match on the last general rule
substituting the group name correctly.
Maybe you can give that rule a try.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-04-05 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 17:05 Norman Walsh
2011-04-04 17:12 ` Randal L. Schwartz
2011-04-05 11:01 ` Norman Walsh
2011-04-05 13:05 ` Leonidas Tsampros [this message]
2011-04-05 14:57 ` Norman Walsh
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=87y63ox2z2.fsf@bifteki.lan \
--to=ltsampros@upnet.gr \
--cc=ding@gnus.org \
--cc=ndw@nwalsh.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).