From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: Gnus '95 and v0.96
Date: 03 Jun 1996 18:01:00 -0700 [thread overview]
Message-ID: <r9qu3wse62b.fsf@fester.cs.washington.edu> (raw)
In-Reply-To: Steven L Baur's message of 25 May 1996 20:30:03 -0700
>>>>> Steven L. Baur writes:
> Starting with Gnus '95 disconnection to the nntp server at exit
> causes a beep.
I've noticed this on occasion, but haven't pinned it down enough to
report it. My guess is that some nntp network stream connection is
left open when I quit from gnus; the server then times out and drops
the connection. Emacs notices that the connection was closed, and
calls some gnus-* function to notify Gnus of this, but the Gnus
variables are long gone, so an error occurrs. Hence the beep.
I may also have seen this after M-x gnus-unload.
--Paul
prev parent reply other threads:[~1996-06-04 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-26 3:30 Steven L Baur
1996-05-27 2:14 ` Mark Borges
1996-06-04 1:01 ` Paul Franklin [this message]
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=r9qu3wse62b.fsf@fester.cs.washington.edu \
--to=paul@cs.washington.edu \
/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).