From: Cor <cor@clsnet.nl>
To: info-gnus-english@gnu.org
Subject: Re: fancy mail splitting
Date: Mon, 21 Dec 2015 17:09:55 +0000 [thread overview]
Message-ID: <87r3ifk9ss.fsf@andromeda.clsnet.nl> (raw)
In-Reply-To: <mailman.311.1450709592.843.info-gnus-english@gnu.org>
Some entity, AKA asjo@koldfront.dk (Adam Sjøgren),
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)
> B.V. writes:
>
>> How about trying "^\\[git/adm\\].*" vs "^Re: \\[git/adm\\].*"
>> I have myself not tried it. But I think the regexp should work!
>
> Adding the ^ doesn't work, but your suggestion gave me the idea of
> having something that matches "Re: [git/adm]" first, and then the usual
> rule after. That works. Although it feels a little kludgey.
It the way the mail-splitting works, sequential and when it hits on the first
matchting reg-expr it drops the message in the box and then goes to the
next incoming message.
Sometimes it really looks like doing magic to get the filtering the way
you want.
Cor
--
Geavanceerde politieke correctheid is niet te onderscheiden van sarcasme
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2015-12-21 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 11:47 Adam Sjøgren
2015-12-21 4:48 ` B.V. Raghav
2015-12-21 14:52 ` Adam Sjøgren
2015-12-21 16:55 ` Adam Sjøgren
[not found] ` <mailman.311.1450709592.843.info-gnus-english@gnu.org>
2015-12-21 17:09 ` Cor [this message]
[not found] <m33cm9oqgi.fsf.p_oster_2000.yahoo.com@post2k.freeuk.com>
2003-02-27 13:50 ` Kai Großjohann
[not found] ` <m3y940wtvq.fsf.p_oster_2000.bigfoot.com@post2k.freeuk.com>
2003-03-02 12:13 ` 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=87r3ifk9ss.fsf@andromeda.clsnet.nl \
--to=cor@clsnet.nl \
--cc=info-gnus-english@gnu.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).