From: Matt Armstrong <matt@lickey.com>
Subject: Re: Protect against servers stepping on each other's toes
Date: Mon, 22 Oct 2001 10:54:27 -0600 [thread overview]
Message-ID: <87g08bwr7g.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <m3pu7g1bkw.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Matt Armstrong <matt@lickey.com> wrote:
>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>>> The trouble is with people who do this:
>>>
>>> (add-to-list 'gnus-secondary-select-methods '(nnml ""))
>>> (add-to-list 'gnus-secondary-select-methods '(nnfolder ""))
> ...
>> I've not yet verified if this happens only because I have '(nnml "")
>> as my primary select method.
>
> It happens because you have '(nnml "") as a select method. It
> doesn't matter whether it's primary, secondary, or foreign.
This is particularly dangerous because operations such as "B c" can
cause select methods to magically appear. I wonder if this is wise.
I also notice that if I gnus-server-regenerate-server my "nnml:"
server, it gets confused by the Mail/archive directory (which is an
nnfolder: thing by default, and is placed in Mail/ by default).
Have all these issues always been present? I think not. Hasn't Gnus
historically only relied on .newsrc.eld for group info, and only
recently looked at files on disk to try to find groups for the
backends?
--
matt
next prev parent reply other threads:[~2001-10-22 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 21:35 Kai Großjohann
2001-10-19 21:49 ` Paul Jarc
2001-10-19 22:37 ` Kai Großjohann
2001-10-19 22:46 ` Paul Jarc
2001-10-20 11:00 ` Kai Großjohann
2001-10-20 6:48 ` Matt Armstrong
2001-10-20 11:03 ` Kai Großjohann
2001-10-20 21:49 ` Matt Armstrong
2001-10-20 22:02 ` Kai Großjohann
2001-10-22 5:35 ` Paul Jarc
2001-10-22 16:54 ` Matt Armstrong [this message]
2001-10-22 20:05 ` Kai Großjohann
2001-10-19 22:42 ` Simon Josefsson
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=87g08bwr7g.fsf@squeaker.lickey.com \
--to=matt@lickey.com \
/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).