From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Protect against servers stepping on each other's toes
Date: Fri, 19 Oct 2001 18:46:19 -0400 [thread overview]
Message-ID: <m3sncfjlim.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafvghbqmsr.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 20 Oct 2001 00:37:08 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> I think much of this could be prevented by using different defaults
>> for different backends, or (like nnmaildir does) by requiring the user
>> to explicitly specify a directory in the server parameters.
>
> It's too late now. Imagine the huge number of people out there with
> (nnml "") in their gnus-secondary-select-methods.
Yeah. Just wishful thinking, I guess.
>> Putting it in the active file would mean we aren't protected against
>> other Emacsen, but in that case a nonpersistent variable will do; it
>> doesn't need to be saved anywhere.
>
> Maybe some crooked mind does something like this:
>
> (add-to-list 'gnus-secondary-select-methods
> '(nnfolder "a"
> (nnfolder-directory "/tmp/a")
> (nnfolder-active-file "/tmp/active")))
> (add-to-list 'gnus-secondary-select-methods
> '(nnfolder "b"
> (nnfolder-directory "/tmp/b")
> (nnfolder-active-file "/tmp/active")))
Well, marking the directory (by whatever means) won't help there.
Should there be a gnus-occupied-active-files as well?
paul
next prev parent reply other threads:[~2001-10-19 22:46 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 [this message]
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
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=m3sncfjlim.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).