Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: "Unplugged" but not offline
Date: Mon, 14 Dec 1998 13:55:51 GMT	[thread overview]
Message-ID: <m3ogp6g76g.fsf@reader.newsguy.com> (raw)


Any one else noticing that v0.65  goes on line even when
"unplugged"? 

Here is what I am seeing.

Start gnus with ppp link up.  Press `J u' or `J s' to get some or all
groups into the agent cache.  Press `J j' and enter a group
(emacs.ding)
Gnus goes right on line to get the headers again.  Even though the
Unplugged sign is showing in the mode line. 

I confirmed this was happening by watching the data transfer with
'pppstats'` 

If I shut down the PPP
link and try entering while "unplugged" I get the message:
>>> writing to process: network is unreachable, nntpd<1>

After restarting ppp connection:

If I shut down gnus and adjust .emacs to start v0.64 and repeat the
same process. All works as it should:  

Start gnus "online" (v0.64)
Press `J u' to download emacs.ding (predicate "true")
Press J j  - enter "emacs.ding"
Gnus enters emacs.ding
(unplugged) and immediately shows a summary buffer.  (No data transfer
occurs)

I've seen no posts about this, so suspect it is something local. 
However the fact that all works normally under v0.64 does seem
to indicate something has gotten out of whack between versions.  The
change-log for v0.65 indicates only minor changes to a couple *.el
files.

Is anyone else seeing this behavior?

-- 
Harry Putnam <reader@newsguy.com>
Running Redhat Linux 5.1
.



             reply	other threads:[~1998-12-14 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-14 13:55 Harry Putnam [this message]
1998-12-14 23:31 ` Kai.Grossjohann
1998-12-15  0:55   ` William M. Perry
1998-12-15  4:42 ` Jeremy D. Zawodny

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=m3ogp6g76g.fsf@reader.newsguy.com \
    --to=reader@newsguy.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.
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).