From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: splitting for dunces
Date: Tue, 05 Oct 2010 08:10:41 +0200 [thread overview]
Message-ID: <ti4od19nku.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m3vd5hvgws.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 04 Oct 2010 22:31:31 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> "Austin F. Frank" <austin.frank@gmail.com> writes:
>
>>> (nnimap-split-methods (("your" "split")))))
>>
>> How would it look if it used fancy splitting?
>
> (nnimap-split-methods '(| (fancy-split blah blah)))
>
> The manual has several fancy split examples, I think.
But split handling has dramatically changed? I ask because my splitting
doesnt work anymore and, to be honest, (as the posts about splitting
indicate) splitting is really tricky to get your head around.
next prev parent reply other threads:[~2010-10-05 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 18:50 Austin F. Frank
2010-10-04 20:17 ` Lars Magne Ingebrigtsen
2010-10-04 20:21 ` Austin F. Frank
2010-10-04 20:31 ` Lars Magne Ingebrigtsen
2010-10-04 21:09 ` Austin F. Frank
2010-10-05 7:09 ` Tassilo Horn
2010-10-05 6:10 ` Richard Riley [this message]
2010-10-05 7:32 ` Gijs Hillenius
2010-10-06 21:50 ` Richard Riley
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=ti4od19nku.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--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).