From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 62845@debbugs.gnu.org
Subject: bug#62845: 29.0.90; nntp-with-open-group-function kills current buffer on timeout
Date: Sat, 06 May 2023 09:58:07 -0700 [thread overview]
Message-ID: <87bkixwg68.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <875y96oulf.fsf@linux-m68k.org> (Andreas Schwab's message of "Sat, 06 May 2023 08:13:48 +0200")
On 05/06/23 08:13 AM, Andreas Schwab wrote:
> On Mai 05 2023, Eric Abrahamsen wrote:
>
>> The answer is, that mechanism is designed to work only once. If the
>> connection is dead or times out, it catches that condition once and
>> tries to re-connect, and won't catch it a second time. So we'd have to
>> be hitting the timeout twice in a row to see this (which definitely
>> happens). I still think it's best just to revert 032969e8c65 on Emacs 29.
>
> When the timeout happens the server buffer is killed. Reopening the
> connection creates a new buffer, but the current buffer remains dead.
But doesn't the call to `nntp-possibly-change-group' at nntp.el:600
re-create the connection, including re-initializing the
nntp-server-buffer, so that when the guts of
`nntp-finish-retrieve-group-infos' are run for the second time, the new
server buffer is found?
I'm having a hell of a time reasoning about this whole flow.
next prev parent reply other threads:[~2023-05-06 16:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 21:47 bug#62845: 29.0.90; nntp-with-open-group-function kills current buffer on timeout Andreas Schwab
2023-04-15 6:45 ` Eli Zaretskii
2023-04-26 23:49 ` Andreas Schwab
2023-04-27 3:08 ` Eric Abrahamsen
2023-05-01 13:19 ` Eli Zaretskii
2023-05-06 0:03 ` Eric Abrahamsen
2023-05-06 3:35 ` Eric Abrahamsen
2023-05-06 5:41 ` Eric Abrahamsen
2023-05-06 6:13 ` Andreas Schwab
2023-05-06 16:58 ` Eric Abrahamsen [this message]
2023-05-06 17:43 ` Andreas Schwab
2023-05-07 5:52 ` Eric Abrahamsen
2023-05-07 7:30 ` Andreas Schwab
2023-05-10 15:53 ` Eli Zaretskii
2023-05-10 18:21 ` Eric Abrahamsen
2023-05-11 10:01 ` Eli Zaretskii
2023-05-11 15:28 ` Eric Abrahamsen
2023-05-06 6:31 ` Eli Zaretskii
2023-05-06 17:05 ` 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
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=87bkixwg68.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=62845@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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).