From: Didier Verna <didier@lrde.epita.fr>
Cc: Gnus Beta Testers <ding@gnus.org>
Subject: Re: [Q] primary / secondary methods differences
Date: 22 May 2001 15:13:10 +0200 [thread overview]
Message-ID: <muxg0dxplw9.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <vafpud1fxda.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "22 May 2001 13:15:29 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> If you can do (add-to-list 'gnus-secondary-select-methods FOO), then
> you can also do (setq gnus-select-method FOO), and vice versa. Was
> this what you meant?
Yup.
The idea behind my question was that the concept of primary /
secondary method is now really obsolete. We should have single
`gnus-select-methodS' variable, and `gnus-no-server' shouldn't rely on levels
(which is also a misfeature), but instead, let you select which of your
gnus-select-methods you want to open for this session.
Implementing `gnus-select-methods' while maintaining backward
compatibility doesn't look too difficult to me. I'm more sceptical on the
latter point though.
--
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 44 08 01 99 didier@xemacs.org
next prev parent reply other threads:[~2001-05-22 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 10:10 Didier Verna
2001-05-22 11:15 ` Kai Großjohann
2001-05-22 13:13 ` Didier Verna [this message]
2001-05-22 15:08 ` Kai Großjohann
2001-05-22 16:04 ` Paul Jarc
2001-05-22 22:28 ` David S. Goldberg
2001-05-22 16:10 ` Didier Verna
2001-05-22 16:20 ` Paul Jarc
2001-05-22 16:34 ` Didier Verna
2001-05-22 17:11 ` Paul Jarc
2001-05-22 17:25 ` Didier Verna
2001-05-22 22:12 ` Simon Josefsson
2001-05-23 9:39 ` Kai Großjohann
2001-05-22 16:38 ` Kai Großjohann
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=muxg0dxplw9.fsf@uzeb.lrde.epita.fr \
--to=didier@lrde.epita.fr \
--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).