From: Adrian Kubala <adrian@sixfingeredman.net>
Subject: Re: how to avoid duplicate server informaiton (bug?)
Date: Mon, 15 Jul 2002 16:23:18 +0200 [thread overview]
Message-ID: <87u1n1t6i1.fsf@sixfingeredman.net> (raw)
In-Reply-To: <m3d6tsydun.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> [...] So secondary select methods can still be referred to in places
> that need a name. Maybe they aren't quite completely
> interchangeable, but I think that would be a bug.
>
> Have you tried defining the server in gnus-secondary-select-methods
> instead of gnus-server-alist?
Aha, this works perfectly. I don't know why, but I was suffering under
the delusion that it was important to have everything defined in
`gnus-server-alist'.
adrian
parent reply other threads:[~2002-07-15 14:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m3d6tsydun.fsf@multivac.cwru.edu>]
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=87u1n1t6i1.fsf@sixfingeredman.net \
--to=adrian@sixfingeredman.net \
/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).