From: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Subject: Re: Check secondary servers in server buffer?
Date: Tue, 24 Jun 2003 01:41:38 +0200 [thread overview]
Message-ID: <m38yrsjr9p.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <84y8zs7trd.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Some people see duplicate servers (eg, "nnimap:du" twice) in their
> server buffer. One of them is a bogus server. It was created
> automatically when some groups had the wrong select method.
I'm kinda wondering at the utility of listing these "known", but
uneditable servers in the server buffer. I think it might make sense
not to display them by default.
On the other hand, I do sometimes `D' a secondary server if it's
sufficiently annoying. So perhaps that's not a good idea.
> The obvious method to find out which one is the right one is to hit
> `e', but `e' on the secondary server (from (add-to-list
> 'gnus-secondary-select-methods '(nnimap "du"
> ...parameters.snipped...))) doesn't give any useful data because
> secondary servers cannot be edited.
>
> WIBNI there was a command to at least see the parameters of such
> secondary servers?
Yes, that might be nice.
> Also it would be nifty if Gnus could prevent such duplicate servers
> somehow. Ideas?
Uhm... it could at least rename the servers in some strange, but
wonderful manner.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-06-23 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 14:28 Kai Großjohann
2003-06-23 23:41 ` Lars Magne Ingebrigtsen [this message]
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=m38yrsjr9p.fsf@quimbies.gnus.org \
--to=larsi@quimbies.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).