From: Phillip Lord <phillip.lord@russet.org.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: gnus nnml/nnimap-split-fancy
Date: Tue, 24 Mar 2020 18:14:32 +0000 [thread overview]
Message-ID: <87bloly60n.fsf@russet.org.uk> (raw)
In-Reply-To: <87v9mv3sdz.fsf@gnu.org> (Amin Bandali's message of "Mon, 23 Mar 2020 13:14:48 -0400")
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.
> [...]
>
>>
>> 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.
next prev parent reply other threads:[~2020-03-24 18:14 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 [this message]
2020-03-24 20:10 ` Amin Bandali
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bloly60n.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.