Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Gnus Beta Testers <ding@gnus.org>
Subject: Re: [RFC] nnmbox and first-time users
Date: Thu, 22 Nov 2001 10:17:56 +0100	[thread overview]
Message-ID: <vaf1yiri2pn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m37ksjydye.fsf@ID-24456.user.dfncis.de> (Christoph Conrad's message of "Wed, 21 Nov 2001 23:08:25 +0100")

Christoph Conrad <christoph.conrad@gmx.de> writes:

>     > In fact I think that slowly the time might have come to change a
>     > lot of important variables in an incompatible manner. That will
>     > at least show the users that something is wrong, and so they can
>     > correct it.
>
> If that is done this change should be documented in a VERY explicit
> manner accompanied by a good "transition description".

Yes.  The Gnus startup code should have some facility to detect the
situation, alert the user to it, and DTRT.

Hm.  Coming to think of it, maybe it is better not to change the
default directories, but rather to have Gnus perform some sanity
checks.

So when Gnus discovers that the user has two servers pointing to the
same directory, Gnus would then barf.

Ah.  We discussed about this a while ago.  Sorry, I completely
forgot.  Yes, I think the sanity check approach is much better.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



      reply	other threads:[~2001-11-22  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 15:15 Didier Verna
2001-11-21 15:46 ` Kai Großjohann
2001-11-21 17:40   ` Paul Jarc
2001-11-22  9:16     ` Kai Großjohann
2001-11-21 22:08   ` Christoph Conrad
2001-11-22  9:17     ` Kai Großjohann [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=vaf1yiri2pn.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@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).