From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 43682@debbugs.gnu.org
Subject: bug#43682: 28.0.50; Clean up nnimap server buffers?
Date: Thu, 01 Oct 2020 03:30:01 +0200 [thread overview]
Message-ID: <87d022wx5y.fsf@gnus.org> (raw)
In-Reply-To: <87tuvfc4ur.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 30 Sep 2020 14:49:32 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> So that's what it's for! That's a mystery solved. It appears that only
> nntp is asynchronous: at least, it's the only backend that implements
> `gnus-asynchronous-p'.
Aha. nnimap should, too.
> nntp.el also contains `nntp-async-{wait,stop-trigger}', but as far as I
> can tell that has nothing to do with gnus-async.el stuff (?). That's the
> code that appears to make use of "extra processes per server", and
> nnimap doesn't have any of that.
Yes, that's a separate thing...
> Not so far as I can tell. sieve.el and sieve-mode.el don't have anything
> to do with Gnus, and gnus-sieve.el is just about building sieve scripts
> from Gnus splitting rules. (Now that you mention it, it would be nice if
> there were a command to edit an IMAP server's sieve scripts from the
> *Server* buffer.)
Right. I think there was once some talk about this stuff, but oy vey
the years...
> I'm inclined to delete the alist altogether, but if we keep it at least
> I can give it a docstring.
No, we should keep it and implement the stuff for gnus-asynchronous-p in
nnimap, too.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-01 1:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 23:37 bug#43682: 28.0.50; Clean up nnimap server buffers? Eric Abrahamsen
2020-09-29 7:42 ` Robert Pluim
2020-09-29 14:51 ` Lars Ingebrigtsen
2020-09-29 18:25 ` Eric Abrahamsen
2020-09-30 1:18 ` Lars Ingebrigtsen
2020-09-30 1:21 ` Lars Ingebrigtsen
2020-09-30 21:49 ` Eric Abrahamsen
2020-10-01 1:30 ` Lars Ingebrigtsen [this message]
2020-10-01 5:09 ` Eric Abrahamsen
2020-10-01 16:01 ` Lars Ingebrigtsen
2020-10-01 17:25 ` Eric Abrahamsen
2021-10-11 12:53 ` Stefan Kangas
2021-10-11 14:41 ` Eric Abrahamsen
2021-10-12 20:50 ` Eric Abrahamsen
2021-10-12 21:33 ` Stefan Kangas
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=87d022wx5y.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43682@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
/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).