From: Lars Ingebrigtsen <larsi@gnus.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: eric@ericabrahamsen.net, 28596@debbugs.gnu.org
Subject: bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news
Date: Thu, 28 Dec 2017 13:07:39 +0100 [thread overview]
Message-ID: <87tvwbgino.fsf@mouse.gnus.org> (raw)
In-Reply-To: <871sjfdaql.fsf_-_@moondust.localdomain> (N. Jackson's message of "Wed, 27 Dec 2017 18:14:42 -0500")
nljlistbox2@gmail.com (N. Jackson) writes:
> Furthermore, I might have been inaccurate when I reported that C-g
> didn't quit at all. I might have not waited long enough. On a
> later hang when I waited after pressing C-g, Emacs came back after
> about two minutes.
C-g should quit Gnus' operations immediately. The "came back after two
minutes" is the typical thing you see on the TLS hang scenario -- I
think Emacs comes unstuck when the server closes the connection (due to
no traffic).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-12-28 12:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:01 bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits N. Jackson
2017-09-25 17:03 ` N. Jackson
2017-09-25 17:14 ` Noam Postavsky
2017-09-26 14:13 ` N. Jackson
2017-09-29 9:10 ` Eli Zaretskii
2017-09-29 15:20 ` Eric Abrahamsen
2017-09-29 17:27 ` N. Jackson
2017-09-29 20:17 ` Eric Abrahamsen
2017-12-02 17:40 ` Eli Zaretskii
2017-12-04 17:14 ` N. Jackson
2017-12-04 17:56 ` Eli Zaretskii
2017-12-22 13:43 ` Eli Zaretskii
2017-12-27 21:00 ` Lars Ingebrigtsen
[not found] ` <871sjfdaql.fsf_-_@moondust.localdomain>
2017-12-28 12:07 ` Lars Ingebrigtsen [this message]
2017-12-28 16:27 ` bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news Eli Zaretskii
2017-12-28 16:29 ` Lars Ingebrigtsen
2017-12-28 17:54 ` Eli Zaretskii
2017-12-28 20:15 ` Lars Ingebrigtsen
2017-12-29 0:14 ` N. Jackson
2018-07-02 17:55 ` Eli Zaretskii
2018-07-03 0:19 ` N. Jackson
2018-07-04 16:50 ` Eli Zaretskii
2018-07-04 18:03 ` N. Jackson
2018-07-04 18:13 ` N. Jackson
2018-07-04 18:30 ` Eli Zaretskii
2018-07-04 18:38 ` N. Jackson
2018-07-04 18:41 ` Eli Zaretskii
2018-07-12 15:33 ` N. Jackson
2018-07-12 15:45 ` Eli Zaretskii
2019-09-27 15:25 ` Lars Ingebrigtsen
2020-07-19 15:44 ` Lars Ingebrigtsen
2018-07-04 18:30 ` Eli Zaretskii
2017-12-11 17:58 ` bug#28596: " N. Jackson
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=87tvwbgino.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=28596@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=nljlistbox2@gmail.com \
/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).