From: Hrvoje Niksic <hniksic@srce.hr>
Cc: ding@ifi.uio.no
Subject: Re: Splitting of ding@ifi
Date: 03 Apr 1997 19:26:40 +0200 [thread overview]
Message-ID: <kigrags81bj.fsf@jagor.srce.hr> (raw)
In-Reply-To: Per Abrahamsen's message of 03 Apr 1997 19:10:33 +0200
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> (| (any "ding@\\(ifi\\.uio\\.no\\|gnus\\.org\\)" "ding.gnus")
Thanks. I think I'll have to use that.
> ("x-from-line" "ding-request" "ding.gnus"))
Do you mean to say that splitting on `X-From-Line' actually works for
you? For me it doesn't, because this header is not created when the
splitting is done -- it's still the plain `From_'. Once the mail is
is saved to Gnus folders, `B q' and `B r' give the correct results,
though.
Still, matching on `X-From-Line' is not usable for me. If it were, it
would be very simple to weed out the mails from any mailing list.
Matching the `From_' header is the one feature from the usual mail
splitting that I miss in fancy mail splitting. Lars, can you make
`nnmail-split-it' construct a non-`:' regexp for a special `from_'
entry? E.g.:
(setq nnmail-split-fancy
'(| ...
(from_ "ding" "ding.list")
...))
Which would construct a regexp like:
"^from .*\\<ding\\>"
or something like that.
P.S.
To the people not familiar with `nnmail-split-fancy': note that just
specifying a ("from " "ding" "ding.list") entry won't work, as it
would insist on having a `:' in the entry (it would create a regexp
to the effect of "from :.*\\<ding\\>"). Matching on `X-From-Line'
doesn't work either, for the reasons stated above.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
main(){printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}
next prev parent reply other threads:[~1997-04-03 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-03 16:45 Hrvoje Niksic
1997-04-03 17:10 ` Per Abrahamsen
1997-04-03 17:26 ` Hrvoje Niksic [this message]
1997-04-03 17:44 ` Per Abrahamsen
1997-04-03 17:51 ` Jason R. Mastaler
1997-04-03 18:48 ` Dewey M. Sasser
1997-04-03 18:55 ` David Moore
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=kigrags81bj.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
--cc=ding@ifi.uio.no \
/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).