From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: respooling nnimap group with nnimap-split-fancy
Date: Fri, 15 Nov 2013 11:55:39 +0700 [thread overview]
Message-ID: <874n7efelw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <i50zgavbzwgi1h.fsf@pedrosilva.pt>
Pedro Silva <psilva@pedrosilva.pt> writes:
> Pedro Silva <psilva@pedrosilva.pt> writes:
>
>> Well, it appears as if it should. Certainly `B t' or `B q` give the
>> expected results. I think the problem is in `gnus-summary-move-mail',
>> but that function is too complex for me to try and hack it.
>
> While the above still stands,
Really? I never got respooling to work with nnimap at all. I remember
looking into the internals a bit at the time, and seeing that respooling
for nnimap eventually just got cross-wired into respooling for nnmail.
That meant it only used nnmail-split-fancy, not nnimap-split-fancy,
which wasn't what I wanted because I still wanted to use
`bbdb/gnus-nnimap-folder-list-from-bbdb'.
Without nnmail-split-fancy set to anything, respooling imap messages
just put them into the default folder: ie from INBOX to mail.misc, which
wasn't what I wanted at all.
>> I should've been clearer. Not only can't I respool, but Gnus doesn't
>> appear to do any kind of splitting whatsoever, on incoming or seen
>> articles.
>
> this was an error on my part (as expected). Upon reading the nnimap
> splitting part of the manual more carefully, I correctly configured Gnus
> to split upon getting email.
That's good news, anyway!
next prev parent reply other threads:[~2013-11-15 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 21:35 Pedro Silva
2013-11-13 1:20 ` Eric Abrahamsen
2013-11-13 14:24 ` Pedro Silva
2013-11-13 20:31 ` Pedro Silva
2013-11-15 4:55 ` Eric Abrahamsen [this message]
2013-11-15 8:49 ` Pedro Silva
2013-11-15 9:09 ` Eric Abrahamsen
2013-12-26 16:40 ` Lars 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=874n7efelw.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).