Re: Protect against servers stepping on each other's toes

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

Matt Armstrong <matt@lickey.com> writes:

> 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 ""))
> 
> And I just spent hours discovering that this happens by default if you
> have:
> 
>     (setq gnus-select-method '(nnml ""))
> 
> And then "B c" a message into an nnfolder:FOO directory.  They both do
> stuff in ~/Mail.  I.e. FOO gets added to ~/Mail/active.

Yes, this is quite bad, for nnml, nnfolder and nnmh all want to use
the same files and directories.  You were right that `B m' to a
non-existing server magically creates it, using the default settings.

But it seems indeed that a variable gnus-occupied-files would be just
right.  It could contain directory names and file names.  And when
Gnus tries to create another server using one of these, a warning or
error message can be issued.

kai
-- 
Lisp is kinda like tpircstsoP