From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Fancy Mail Splitting documentation needs improved?
Date: Tue, 11 Jan 2011 19:58:24 +0100 [thread overview]
Message-ID: <m362tvnu7j.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87oc7qp0ya.fsf@anar.kanru.info>
Kan-Ru Chen <kanru@kanru.info> writes:
> Of course I can write
>
> (| ("x-bogosity" "spam" "mail.spam")
> ("x-spam-status" "yes" "mail.spam")
> "mail.misc")
>
> See, for every FIELD I have to duplicate the SPLIT, "mail.spam" in this
> case.
Yes, I think that's the case.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-11 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 18:02 Tommy Kelly
2010-12-20 9:28 ` Kan-Ru Chen
2010-12-20 17:11 ` Lars Magne Ingebrigtsen
2010-12-21 3:36 ` Kan-Ru Chen
2011-01-02 6:56 ` Lars Magne Ingebrigtsen
2011-01-09 13:00 ` Kan-Ru Chen
2011-01-09 13:27 ` Andreas Schwab
2011-01-09 15:10 ` Kan-Ru Chen
2011-01-11 18:58 ` Lars Magne Ingebrigtsen [this message]
2010-12-20 17:16 ` Lars Magne Ingebrigtsen
2010-12-20 17:53 ` Tommy Kelly
2010-12-20 17:56 ` Lars Magne Ingebrigtsen
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=m362tvnu7j.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).