From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnslashdot - quickref quide please
Date: 05 Dec 1999 23:13:05 +0100 [thread overview]
Message-ID: <vaf9039dojy.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Jake Colman's message of "01 Dec 1999 18:42:14 -0500"
Jake Colman <colman@ppllc.com> writes:
> >>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> LMI> The easiest way is to put it into your secondary select methods, I
> LMI> think.
>
> What exactly would be added to the gnus-secondary-select-methods?
The existing documentation already says this. See the first dozen
lines or so in the `Slashdot' node.
> Is this an easier approach than the topics-based approach advocated
> in an earlier thread? Or do the two go hand-in-hand?
They do different things altogether. It's like asking whether an
automatic gear shift is easier than power steering and whether the two
go hand in hand...
By adding nnslashdot to the secondary select methods or via the server
buffer, you enable Gnus to access the groups. The topic-based
approach works with both and tells Gnus where to put newly-discovered
nnslashdot groups.
kai
--
A preposition is not a good thing to end a sentence with.
next prev parent reply other threads:[~1999-12-05 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-16 22:38 Jake Colman
1999-11-16 22:44 ` Kai Großjohann
1999-12-01 15:38 ` Lars Magne Ingebrigtsen
1999-12-01 23:42 ` Jake Colman
1999-12-05 22:13 ` Kai Großjohann [this message]
1999-12-06 19:54 ` Jake Colman
1999-12-06 22:39 ` Kai Großjohann
1999-12-07 3:53 ` Jack Vinson
1999-12-07 18:39 ` dave-mlist
1999-12-08 4:25 ` Jake Colman
1999-12-08 5:29 ` Jack Vinson
1999-12-10 11:27 ` Peter Makholm
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=vaf9039dojy.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).