From: Bjorn Halvor Solberg <bjorn@geocities.com>
Cc: ding@gnus.org
Subject: Re: Problem with nnslashdot
Date: 17 Mar 2000 15:11:14 -0800 [thread overview]
Message-ID: <m3g0tp6vl9.fsf@pacbell.net> (raw)
In-Reply-To: Niels Olof Bouvin's message of "Thu, 16 Mar 2000 11:11:14 +0100"
Niels Olof Bouvin writes:
> Jack Vinson <JackVinson@yahoo.com> writes:
> [...]
>> Looking into this further, it was a problem with my build of w3. New
>> build, no problem.
> I tried to update my w3 to pre.46 (the newest I could find) - no luck, still
> the same behaviour.
I wonder, does the lack of response to this problem stem from that noone
else are having trouble using nnslashdot, or that everyone else are too
busy doing other things to read Slashdot in Gnus? :)
Bjorn.
next prev parent reply other threads:[~2000-03-17 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 6:50 Niels Olof Bouvin
2000-03-14 0:47 ` Jack Vinson
2000-03-16 0:37 ` Jack Vinson
2000-03-16 10:11 ` Niels Olof Bouvin
2000-03-17 23:11 ` Bjorn Halvor Solberg [this message]
2000-03-16 1:31 ` Bjorn Halvor Solberg
-- strict thread matches above, loose matches on Subject: below --
1999-11-24 15:21 problem " Sorgum Vargus
1999-11-24 16:31 ` Eric Marsden
1999-12-01 20:44 ` Lars Magne Ingebrigtsen
1999-12-01 20:47 ` 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=m3g0tp6vl9.fsf@pacbell.net \
--to=bjorn@geocities.com \
--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).