From: Gunnar Evermann <ge204@eng.cam.ac.uk>
Cc: ding@gnus.org
Subject: Re: xemacs hang while gnus is trying to cope with flakey server
Date: 20 Nov 2000 13:07:49 +0000 [thread overview]
Message-ID: <mqqpujq94gq.fsf@eng.cam.ac.uk> (raw)
In-Reply-To: Laura Conrad's message of "20 Nov 2000 07:54:39 -0500"
Laura Conrad <lconrad@laymusic.org> writes:
> The usual symptom is that gnus takes forever to come back when I say
> "g", and then when I ^g out of it, it does deny the server, but also
> seems to have forgotten the marks in all of the groups in that server.
>
> Last night, however, even ^G didn't get out of the loop, and I got
> this backtrace when I killed the xemacs:
Please always include the output of 'M-x describe-installation' in bug
reports. I assume this is 21.1 on some kind of Linux? Did you type the
C-g in an X window or a TTY (e.g. gnuclient -nw)?
> Lisp backtrace follows:
>
> # (unwind-protect ...)
> open-network-stream-internal("nntpd" #<buffer " *server news-east.speakeasy.net nntp *nntpd**"> "news-east.speakeasy.net" "nntp")
yes, this is a bug in XEmacs. We are working on a solution.
Gunnar
next prev parent reply other threads:[~2000-11-20 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 12:54 Laura Conrad
2000-11-20 13:07 ` Gunnar Evermann [this message]
2000-11-20 13:20 ` ShengHuo ZHU
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=mqqpujq94gq.fsf@eng.cam.ac.uk \
--to=ge204@eng.cam.ac.uk \
--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).