From: Simon Josefsson <jas@extundo.com>
Subject: Re: Problem with respooling
Date: Sat, 08 Nov 2003 14:14:46 +0100 [thread overview]
Message-ID: <iluvfpvq9x5.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4n7k2b302w.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Sat, 08 Nov 2003 00:23:35 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sat, 08 Nov 2003, jas@extundo.com wrote:
>
>> Respooling is nnmail specific, if I recall correctly. It assumes
>> the backend looks in nnmail-split-methods to decide the group name.
>
> OK, but is nnimap a nnmail backend?
No. (But it sometimes try to pretend to be one, by using nnmail
variables.)
> If not, what should `B r' do in nnimap groups?
Using `nnimap-split-rule' seems reasonable.
>> The group=nil mode of operation is not documented, so I think that
>> should be fixed before any code is altered.
>
> Right, I have no idea where the nil group is coming from! I tried to
> trace the code but it does a lot of "make a string and call it as a
> function name" acrobatics that, to me, are confusing. Anyhow, if
> nnimap groups shouldn't use `B r', that's fine, but it's not
> documented or prevented right now - so I want to help do those things.
Right. I think for Oort Gnus, the best is to document that respooling
only works on nnmail groups (and mention that nnimap isn't one), and
in No Gnus document the group=nil idiom and have nnimap support it by
matching the message against the normal nnimap split rules.
next prev parent reply other threads:[~2003-11-08 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vkislw4gek.fsf@horse01.daimi.au.dk>
[not found] ` <4nbrroyq9r.fsf@koz.bwh.harvard.edu>
2003-11-07 20:07 ` Ted Zlatanov
2003-11-08 1:34 ` Simon Josefsson
2003-11-08 5:23 ` Ted Zlatanov
2003-11-08 13:14 ` Simon Josefsson [this message]
2003-11-10 15:55 ` 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=iluvfpvq9x5.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).