From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus request scan issue : backtrace
Date: Tue, 05 Oct 2010 12:31:21 -0500 [thread overview]
Message-ID: <878w2clf6e.fsf@lifelogs.com> (raw)
In-Reply-To: <m31v845zlo.fsf@quimbies.gnus.org>
On Tue, 05 Oct 2010 19:16:51 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>>>> (nnimap-split-methods nnimap-split-fancy)
LMI> That should probably be nnmail-split-fancy, or a fancy split
LMI> directly...
Right. So many nn????-*-* strings...
Richard: if that's set to nnimap-split-fancy, then nnimap-split-fancy
must be a function as in my example. I'll update my splitting example
and post it here again when I can.
Ted
next prev parent reply other threads:[~2010-10-05 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 14:23 Richard Riley
2010-10-05 14:54 ` Ted Zlatanov
2010-10-05 15:26 ` Richard Riley
2010-10-05 15:41 ` Ted Zlatanov
2010-10-05 15:49 ` Richard Riley
2010-10-05 17:16 ` Lars Magne Ingebrigtsen
2010-10-05 17:31 ` Ted Zlatanov [this message]
2010-10-05 18:21 ` Tibor Simko
2010-10-06 10:09 ` Richard Riley
2010-10-05 18:47 ` Andreas Schwab
2010-10-05 19:25 ` Ted Zlatanov
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=878w2clf6e.fsf@lifelogs.com \
--to=tzz@lifelogs.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).