Gnus development mailing list
 help / color / mirror / Atom feed
From: Matt Armstrong <matt@lickey.com>
Subject: Re: Protect against servers stepping on each other's toes
Date: Sat, 20 Oct 2001 15:49:29 -0600	[thread overview]
Message-ID: <871yjyq8wm.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <vaf4rou1slg.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 20 Oct 2001 13:03:23 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> 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.

I agree completely.  Even a fairly cryptic error message would be
better than the current behavior.  :-)


-- 
matt



  reply	other threads:[~2001-10-20 21:49 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 [this message]
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=871yjyq8wm.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).