From: Bodertz <bodertz@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: nnimap-split-download-body removed?
Date: Tue, 01 Dec 2020 01:46:46 -0700 [thread overview]
Message-ID: <87wny1q5ft.fsf@gmail.com> (raw)
In-Reply-To: <87360qqju4.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 30 Nov 2020 19:35:47 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Continuing our baseless speculation without looking at the code... I
> wonder if it would be even possible to do this: it would require
> either running splitting twice (once to split simpler messages, and
> return a list of messages that needed further downloading and
> re-splitting), or pausing in the middle of splitting to download
> messages.
Yeah, I really don't understand much of the code.
`nnimap-split-incoming-mail' runs before `nnimap-fetch-inbox', so that
might be the place which would need to be altered so that it first
fetches the new article's headers with a new function like
`nnimap-fetch-inbox' but which just ignores `nnimap-split-download-body'
and then split those, but then `nnmail-split-it' would need to somehow
know not to split messages which operate on the body. So that seems
complicated.
Maybe having the function given in the `(: function)' split do the work
of downloading the message would be easier. I don't know if that's
possible, though.
> Anyway, let me send in a bug report for the simpler change.
Thanks for that.
> I'll mention your other request, and see if anyone else has a point of
> view.
Thanks for that as well.
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-12-01 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 15:03 Bodertz
2020-11-30 17:10 ` Eric Abrahamsen
2020-12-01 0:15 ` Bodertz
2020-12-01 1:51 ` Eric Abrahamsen
2020-12-01 3:04 ` Bodertz
2020-12-01 3:35 ` Eric Abrahamsen
2020-12-01 8:46 ` Bodertz [this message]
2020-12-01 18:26 ` Eric Abrahamsen
2020-12-02 7:18 ` Bodertz
2020-12-02 20:34 ` Eric Abrahamsen
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=87wny1q5ft.fsf@gmail.com \
--to=bodertz@gmail.com \
--cc=eric@ericabrahamsen.net \
--cc=info-gnus-english@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 NNTP newsgroup(s).