From: Jesse Alama <alama@stanford.edu>
Subject: Re: nnrss doesn't work at all for me.
Date: Sun, 20 Feb 2005 22:51:04 -0800 [thread overview]
Message-ID: <m2vf8mbe3r.fsf@DN800c9108.Stanford.EDU> (raw)
In-Reply-To: <m3oeeecxd2.fsf@papaya.bactrian.org>
Hi David,
I had the same trouble (with Gnus, with documentation) when I wanted
to subscribe to some RSS groups. My solution: in the *Group* buffer,
type `G R', then enter the URL.
Warm regards,
Jesse
PS I found this solution by talking to the friendly folks on #gnus on
irc://irc.freenode.net
David Carlton <carlton@bactrian.org> writes:
> I'm using Gnus 5.10.6 (as distributed with XEmacs, where I'm using the
> Fedora Core 2 RPMs for the latter). The manual distributed with
> XEmacs doesn't mention rss, but googling for 'gnus rss' turns up
> <http://www.gnus.org/manual/gnus_193.html>. The manual on that web
> page claims to be for Gnus 5.10.2; frankly, I'm dubious about that.
> So:
>
> * Should I expect to be able to use nnrss with 5.10.6? (And what Gnus
> version is the online manual for?)
>
> Anyways, optimistically following the instructions listed on that web
> page, I type 'B', then nnrss, then enter
> http://slashdot.org/slashdot.rss. It asks me if I want to download
> extra categories. If I answer 'n', I get an empty buffer. If I
> answer 'y', I get a buffer looking like this:
>
> K 0: Business: general.CRM news
> K 0: Business: general.Entrepreneur news
> K 0: Business: general.Human resources news
> K 0: Business: general.IP and patents news
> K 0: Business: general.Job markets news
> K 0: Business: general.Law news
> ...
>
> Which isn't very useful.
>
> Am I doing something wrong, does nnrss just not work with the version
> of Gnus I'm using, or what?
--
Jesse Alama | alama@stanford.edu | http://www.stanford.edu/~alama
next prev parent reply other threads:[~2005-02-21 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 5:09 David Carlton
2005-02-21 6:51 ` Jesse Alama [this message]
2005-02-22 0:52 ` David Carlton
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=m2vf8mbe3r.fsf@DN800c9108.Stanford.EDU \
--to=alama@stanford.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).