From: Amin Bandali <bandali@gnu.org>
To: help-gnu-emacs@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: gnus nnml/nnimap-split-fancy
Date: Tue, 24 Mar 2020 16:10:10 -0400 [thread overview]
Message-ID: <87sghx3465.fsf@gnu.org> (raw)
In-Reply-To: <87bloly60n.fsf@russet.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
Phillip Lord <phillip.lord@russet.org.uk> writes:
> Amin Bandali <bandali@gnu.org> writes:
>
>> Phillip Lord <phillip.lord@russet.org.uk> writes:
>>
>>> Is there a way to get either nnml or nnimap split across backends?
>>>
>>
>> Not that I know of, but I too would love to be able to split across
>> backends, e.g. from one nnimap backend to another, or from an nnimap
>> backend to an nnfolder one perhaps.
>
>
> Yes, and I don't understand why not. I wonder how big a fix it would be.
>
I have no idea. Lars, Eric, what do you think?
>
>
>> [...]
>>
>>>
>>> Finally, with nnimap splitting, the default group is "bogus". How I
>>> specific "don't do anything with the message, but leave it where it
>>> is"?
>>>
>>
>> I manually specify the name of the inbox like so:
>>
>> (nnimap "gnu"
>> ;; [...]
>> (nnimap-inbox "INBOX")
>> (nnimap-split-methods 'nnimap-split-fancy)
>> (nnimap-split-fancy (|
>> ;; [...]
>> ;; otherwise, leave mail in INBOX
>> "INBOX")))
>>
>> Not sure if there's a better way.
>
> And does that work? I mean it doesn't remove the message and then read
> add it or some such? I presume that splitting only happens over unread
> messages, because I use "inbox infinite" -- so I get a lot of messages
> there.
Yeah it works fine for me, at least for nnimap, I'd imagine because of
C-h v nnimap-unsplittable-articles RET, defaulting to '(%Deleted %Seen),
meaning that messages marked as deleted or read should not be subject to
splitting. That said, I think an explicit "do nothing" rule would be
nice indeed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-03-24 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 12:12 gnus nnml/nnimap-split-fancy Phillip Lord
2020-03-23 17:14 ` Amin Bandali
2020-03-24 18:14 ` Phillip Lord
2020-03-24 20:10 ` Amin Bandali [this message]
2020-03-24 21:20 ` Lars Ingebrigtsen
2020-03-25 22:00 ` Phillip Lord
2020-03-25 23:19 ` Eric Abrahamsen
2020-03-25 22:09 ` Phillip Lord
2020-03-30 18:03 ` Phillip Lord
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sghx3465.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
--cc=larsi@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 read-only IMAP folder(s) and NNTP newsgroup(s).