From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: 53070@debbugs.gnu.org
Subject: bug#53070: 27.2; Message "Server closed connection" not verbose enough
Date: Fri, 07 Jan 2022 08:13:42 -0800 [thread overview]
Message-ID: <87fspza5hl.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87o84nhq0j.fsf@vagabond.tim-landscheidt.de> (Tim Landscheidt's message of "Fri, 07 Jan 2022 09:08:28 +0000")
Tim Landscheidt <tim@tim-landscheidt.de> writes:
[...]
> It would be more helpful if the error message read "Server
> news.gmane.io closed connection" or, to avoid any ambiguity,
> "NNTP server news.gmane.io closed connection".
Thank you for reporting this, and I think Robert's patch would be very
welcome.
> (Side note: If such a hiccup happens, it sometimes appears
> that the *Group* buffer is not updated with regard to number
> of unread messages per group, etc. for /other/ servers that
> were successfully contacted. I don't know if Gnus is more
> aggressive than it needs to be here; if it encounters an er-
> ror when trying to contact a POP3 server, it will just ask
> nicely and continue on.)
How recent is your Emacs? In 032969e8 (end of October) I put in a patch
which switched NNTP failures from raising an error -- which interrupted
the whole update process -- to simply reporting the failure. What you
describe sounds like the behavior I'd observed before making that
change.
next prev parent reply other threads:[~2022-01-07 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 9:08 bug#53070: 27.2; Message "Server closed connection" not verbose enough Tim Landscheidt
2022-01-07 9:35 ` Robert Pluim
2022-01-14 8:04 ` Lars Ingebrigtsen
2022-01-07 16:13 ` Eric Abrahamsen [this message]
2022-01-07 22:12 ` Tim Landscheidt
2022-01-07 22:41 ` 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=87fspza5hl.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=53070@debbugs.gnu.org \
--cc=tim@tim-landscheidt.de \
/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).