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 18:01:15 +0200 [thread overview]
Message-ID: <87o8lmq6k4.fsf@gnus.org> (raw)
In-Reply-To: <871rii7cso.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 30 Sep 2020 22:09:11 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> It's possible (I'm not claiming to understand all the code) that all we
> would need to do is fix `gnus-async-wait-for-article' to replace its
> calls to `nntp-find-connection' and `nntp-accept-process-output' with
> something generalized. Those two functions deal with directly with
> `nntp-connection-alist', so we'd need something that would do the
> equivalent with `nnimap-connection-alist'.
Yup.
> Anyway, in the interest of completing this far less ambitious patch: if
> the nnimap connection has timed out, we should remove this connection
> from `nnimap-connection-alist', so this version of the patch does that.
> If async has opened a second connection, I guess we should leave that
> alone, though I don't have too much confidence that the whole process
> will recover gracefully from the main connection dying...
Well, the connections are separate, and there's all kinds of reasons for
the server to close a connection, so...
> + (unless (memq (process-status (get-buffer-process buffer))
> + '(open run))
Aka `process-live-p'.
Otherwise looks fine to me (but I haven't tested the code).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-01 16:01 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
2020-10-01 5:09 ` Eric Abrahamsen
2020-10-01 16:01 ` Lars Ingebrigtsen [this message]
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=87o8lmq6k4.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).