From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 44981@debbugs.gnu.org
Subject: bug#44981: 28.0.50; Restore nnimap-split-download-body?
Date: Sat, 05 Dec 2020 11:48:55 -0800 [thread overview]
Message-ID: <87r1o4nie0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87wnxw1c0y.fsf@tcd.ie> (Basil L. Contovounesios's message of "Sat, 05 Dec 2020 15:57:17 +0000")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I'm not sure why spam.el would need to work on the default value of
>> `nnimap-split-download-body'. If spam.el determines that widening is
>> needed, it's going to download message bodies across the board anyway.
>> The only reason to preserve the user's own customization would be if the
>> user later unloaded spam.el -- then it should restore the previous
>> value. But how often would that actually be useful?
>>
>> In principle, TRT would be to have spam.el let-bind a variable around
>> the splitting process. But I don't think the code is set up that way:
>> all the spam.el stuff happens "inside" the splitting process, not around
>> it.
>
> How about the attached kludgy but conservative dance?
It seems like a lot of work for something no one's likely to even
notice! But since you've already done the work I wouldn't object :)
next prev parent reply other threads:[~2020-12-05 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 4:12 bug#44981: 28.0.50; Restore nnimap-split-download-body? Eric Abrahamsen
2020-12-02 10:28 ` Lars Ingebrigtsen
2020-12-02 21:01 ` Basil L. Contovounesios
2020-12-02 21:18 ` Eric Abrahamsen
2020-12-03 8:03 ` Lars Ingebrigtsen
2020-12-02 23:56 ` Eric Abrahamsen
2020-12-03 8:10 ` Lars Ingebrigtsen
2020-12-03 18:20 ` Eric Abrahamsen
2020-12-04 10:45 ` Basil L. Contovounesios
2020-12-04 18:39 ` Eric Abrahamsen
2020-12-05 15:57 ` Basil L. Contovounesios
2020-12-05 19:48 ` Eric Abrahamsen [this message]
2020-12-06 12:06 ` Basil L. Contovounesios
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=87r1o4nie0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=44981@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).