From: Andreas Schwab <schwab@linux-m68k.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
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: Sun, 07 May 2023 09:30:43 +0200 [thread overview]
Message-ID: <878re0y4ws.fsf@linux-m68k.org> (raw)
In-Reply-To: <873548wuwe.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 06 May 2023 22:52:17 -0700")
On Mai 06 2023, Eric Abrahamsen wrote:
> But `nntp-possibly-change-group' re-initializes `nntp-server-buffer' to
> a new buffer, and the `nntp-find-connection-buffer' inside
> `nntp-retrieve-group-data-early' uses the value of `nntp-server-buffer'
> to find its process. My reading is that each time the with-open-group
> function runs, its `bodyfun' lambda should get a new opportunity to find
> a live `nntp-server-buffer'.
But that only happens when nntp-report-error is called. The timer has
already killed the process buffer long before, and in the mean time the
function happily butchers around in a random buffer.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-05-07 7:30 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
2023-05-06 17:43 ` Andreas Schwab
2023-05-07 5:52 ` Eric Abrahamsen
2023-05-07 7:30 ` Andreas Schwab [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878re0y4ws.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=62845@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.