From: Lars Ingebrigtsen <larsi@gnus.org>
To: help-gnu-emacs@gnu.org
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: gnus nnml/nnimap-split-fancy
Date: Tue, 24 Mar 2020 22:20:15 +0100 [thread overview]
Message-ID: <874kud5u28.fsf@gnus.org> (raw)
In-Reply-To: <87sghx3465.fsf@gnu.org> (Amin Bandali's message of "Tue, 24 Mar 2020 16:10:10 -0400")
Amin Bandali <bandali@gnu.org> writes:
>> 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?
The way splitting happens is that it happens inside the backend. So the
splitting would have to be reorganised to happen in Gnus instead for
that to work.
next prev parent reply other threads:[~2020-03-24 21:20 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
2020-03-24 21:20 ` Lars Ingebrigtsen [this message]
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=874kud5u28.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eric@ericabrahamsen.net \
--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.
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).