Gnus development mailing list
 help / color / mirror / Atom feed
From: Didier Verna <didier@lrde.epita.fr>
Subject: [RFC] nnmbox and first-time users
Date: Wed, 21 Nov 2001 16:15:51 +0100	[thread overview]
Message-ID: <muxbshwcfyw.fsf@uzeb.lrde.epita.fr> (raw)


        The nnmbox backend uses ~/.mbox by default. IMHO, it should have used
something more gnusy (or is there a rationale behind this value ?), at least
honoring gnus-directory, and probably message-directory. Obviously, I
understand that such an important variable cannot have its default changed
like that.

        Still, there might be interference problems with other software that
use ~/.mbox (like mutt). I've done a quick test with an mbox already filled
with one message by mutt, and starting a first-time gnus session. The message
is not erased, but will not be seen by gnus. That can be disconcerting and I
suspect much more serious stuff can happen with other software / other
situations.

        What if we made first-time gnus check if nnmbox is used, if the mbox
file already exists, and in that case, issue a warning, advice to move it away
and abort ?

-- 
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier

EPITA / LRDE, 14-16 rue Voltaire   Tel.+33 (1) 53 14 59 47
94276 Le Kremlin-Bicêtre, France   Fax.+33 (1) 53 14 59 22   didier@xemacs.org



             reply	other threads:[~2001-11-21 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 15:15 Didier Verna [this message]
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

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=muxbshwcfyw.fsf@uzeb.lrde.epita.fr \
    --to=didier@lrde.epita.fr \
    /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).