From: Ted Stern <stern@tera.com>
Subject: can't read nnslashdot
Date: 24 Mar 2000 10:43:57 -0800 [thread overview]
Message-ID: <yccg0tgxl76.fsf@orff.sea.tera.com> (raw)
There must be something in my settings, I just don't know what to look for.
I have tried browsing slashdot and also using gnus-secondary-select-methods,
but gnus sits there for ages until I hit ^G to quit. Here is a snippet from
the *Messages* buffer:
Connecting to slashdot.org...
Opening nnslashdot server on slashdot.org...
Reading active file...
Contacting host: slashdot.org:80
Wrote /home/users/stern/.url/history
Quit
error in process sentinel: Trying to parse headers in odd buffer: *http slashdot.org:80*<6> [2 times]
I am using Emacs-20.3, and the latest cvs versions of gnus, url and w3.
Any ideas? Suggestions? TIA,
--
Ted Stern Porting/Tuning/Analysis, Applications & Libraries
Tera Computer Company http://www.tera.com
411 First Avenue South, Suite 600 Direct 206/701-2182, Main 701-2000
Seattle, WA 98104-2860 Fax1 206/701-2205, Fax2 701-2500
next reply other threads:[~2000-03-24 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 18:43 Ted Stern [this message]
2000-03-25 0:31 ` Michael Harnois
2000-03-25 3:09 ` Jack Vinson
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=yccg0tgxl76.fsf@orff.sea.tera.com \
--to=stern@tera.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).