From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: nntp hangs
Date: Thu, 01 Mar 2012 17:04:21 +0900 [thread overview]
Message-ID: <b4m62eoeohm.fsf@jpl.org> (raw)
Hi,
I frequently meet with Ma Gnus hanging up on news reading on
the nntp servers that go timeout in a minute. The typical one
is news.gmane.org. Several minutes after quitting reading
a group, it happens when I type `M-g' to check new articles in
the group. At that time the echo area shows
Opening nntp server on gmane...done
but Emacs gets to hang up. `C-g' and to retype `M-g' immediately
will help. By turning `debug-on-quit' on, the following bt is
gotten when typing `C-g':
Debugger entered--Lisp error: (quit)
signal(quit nil)
[...]
nntp-with-open-group-function (nil "gmane" nil -BODYFUN)
(nntp-with-open-group nil server (when (nntp-send-command "^[245].*\n" "GRO
nntp-request-group("gmane.emacs.diffs" "gmane" nil ("nntp+gmane:gmane.emac
gnus-activate-group("nntp+gmane:gmane.emacs.diffs" scan nil (nntp "gmane"
gnus-group-get-new-news-this-group(nil)
call-interactively(gnus-group-get-new-news-this-group nil nil)
Where -BODYFUN is as follows:
(lambda nil
(when (nntp-send-command "^[245].*\n" "GROUP" group)
(let ((entry (nntp-find-connection-entry nntp-server-buffer)))
(setcar (cddr entry) group))))
Though I haven't found the cause yet, I guess Gnus tries to send
the GROUP command to the server, to which the connection has
been closed any longer by the server. IIRC, that didn't happen
till recently.
next reply other threads:[~2012-03-01 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 8:04 Katsumi Yamaoka [this message]
2012-03-01 14:39 ` Tassilo Horn
2012-03-02 17:05 ` Ted Zlatanov
2012-03-05 11:10 ` Katsumi Yamaoka
2012-03-05 18:51 ` Joseph Gay
2012-03-06 8:09 ` Katsumi Yamaoka
2012-03-10 0:37 ` Lars Magne Ingebrigtsen
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=b4m62eoeohm.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).