From: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: ding@gnus.org
Subject: Re: `nnmail-split-fancy' regexp
Date: 25 Jun 1999 09:51:00 -0300 [thread overview]
Message-ID: <or1zf05tqj.fsf@saci.lsd.dcc.unicamp.br> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "25 Jun 1999 13:48:20 +0200"
On Jun 25, 1999, Kai.Grossjohann@CS.Uni-Dortmund.DE wrote:
> Well, would this work? "\\(^\\|.*[< ,]\\)libtool@gnus\\.org"
Nope, it's not a beginning-of-line (or of string) for `^' to match.
> I think you're using the wrong approach, though. Most mailing lists
> contain a header which uniquely idenfies the mails.
But there are messages that are posted to multiple mailing lists, and
I'd receive multiple copies of the message with different
Sender/X-loop/whatever headers. If I relied on them, I'd have to
disable discarding of duplicates, which I don't want to do, or I'd
have to live without cross-posting.
Anyway, my particular problem doesn't matter much; the fact is that
there's no way to make sure you're not getting the implicit .* to
match a `-' you don't want it to match. Although it is nice to have
full words by default, `-' is a word separator, so it doesn't always
get it right.
> Hm. How does one match "Sender: foo-owner@frob.org" exactly with
> fancy splitting? Maybe it's not so easy after all :-(
Precisely.
> (| ("Sender" "bug-libtool-owner" (& "bug-libtool group" "libtool group"))
> ("Sender" "libtool-owner" "libtool group"))
Nope, I don't want cross-posting where it doesn't belong, i.e., if a
message was only posted to bug-libtool-owner, it shouldn't appear in
the libtool group.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
{oliva,Alexandre.Oliva}@dcc.unicamp.br aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists
next prev parent reply other threads:[~1999-06-25 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 8:25 Petersen Jens-Ulrik (NRC/Tokyo)
1999-06-24 18:26 ` Per Abrahamsen
1999-06-25 7:52 ` Petersen Jens-Ulrik (NRC/Tokyo)
1999-06-25 9:48 ` Kai.Grossjohann
1999-06-25 10:28 ` Alexandre Oliva
1999-06-25 11:48 ` Kai.Grossjohann
1999-06-25 12:51 ` Alexandre Oliva [this message]
1999-06-25 9:42 ` Alexandre Oliva
1999-06-25 12:25 ` Per Abrahamsen
1999-06-28 17:33 ` Lars Magne Ingebrigtsen
1999-06-28 18:14 ` Aaron M. Ucko
1999-06-28 18:49 ` Per Abrahamsen
1999-06-28 19:11 ` Alexandre Oliva
1999-07-04 3:07 ` Lars Magne Ingebrigtsen
1999-07-04 21:15 ` Alexandre Oliva
1999-07-04 22:54 ` Alexandre Oliva
1999-07-07 14:28 ` Toby Speight
1999-07-07 17:38 ` Alexandre Oliva
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=or1zf05tqj.fsf@saci.lsd.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--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).