From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: gnus-secondary-select-methods: what's the point?
Date: Wed, 27 May 2009 00:52:02 +0200 [thread overview]
Message-ID: <8763fnbhpp.fsf@engster.org> (raw)
In-Reply-To: <m2tz37wts8.fsf@boostpro.com> (David Abrahams's message of "Tue, 26 May 2009 15:25:43 -0400")
David Abrahams <dave@boostpro.com> writes:
> I'm trying to figure out what the point is of setting up
> gnus-secondary-select-methods. I can go into my *Servers* buffer and
> add servers that will persist across sessions without ever changing it.
> So what does it really do?
There isn't much difference between secondary and foreign groups. My
guess would be that native, secondary and foreign groups more or less
evolved historically, but I might be wrong.
Regarding gnus-secondary-select-methods, you probably already found the
following remark in the docs:
,----
| A slightly different approach to foreign groups is to set the
| `gnus-secondary-select-methods' variable. The select methods listed in
| this variable are in many ways just as native as the
| `gnus-select-method' server. They will also be queried for active
| files during startup (if that's required), and new newsgroups that
| appear on these servers will be subscribed (or not) just as native
| groups are.
`----
In a nutshell, I see the following differences:
* native method: doesn't have a prefix and will be ignored if you start
through gnus-no-server (only for groups with level >2).
* secondary methods: do have a prefix, will not be ignored by
gnus-no-server (?).
* foreign methods: won't be queried for new groups on startup. Server
vanishes if you unsubscribe from all its groups.
Otherwise, it's more or less a matter of taste. Some people like to have
their full configuration in .gnus, and not in .newsrc.eld, since the
latter isn't meant to be edited by hand.
-David
next prev parent reply other threads:[~2009-05-26 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 19:25 David Abrahams
2009-05-26 22:52 ` David Engster [this message]
2009-05-27 1:01 ` Mark Plaksin
2009-05-27 8:37 ` David Engster
2009-05-27 15:58 ` Mark Plaksin
2009-07-08 19:21 ` Ted Zlatanov
2009-05-27 19:57 ` David Abrahams
2009-05-27 19:57 ` David Abrahams
2009-05-27 22:08 ` David Engster
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=8763fnbhpp.fsf@engster.org \
--to=deng@randomsample.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).