From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: [RFC] nnmbox and first-time users
Date: Thu, 22 Nov 2001 10:16:10 +0100 [thread overview]
Message-ID: <vaf6683i2sl.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3adxgrpij.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Wed, 21 Nov 2001 12:40:14 -0500")
prj@po.cwru.edu (Paul Jarc) writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>> We need to change the files and directories used for the servers to
>> something unique. For example, use ~/Gnus/nnml/unnamed/ for the
>> server (nnml ""), and so on.
>
> That would (I assume) interfere with a server called (nnml "unnamed").
> Instead, we could use ~/Gnus/nnml/ for (nnml "") and
> ~/Gnus/nnml+unnamed/ for (nnml "unnamed"). Or something like that.
Good idea.
> (nnml "foo") would still interfere with (nnml "foo/bar"). Should we
> worry about such cases? Slashes in server addresses could be encoded
> in directory names somehow, but I don't know if it's worth the effort.
> How likely is it that someone would use such an address, and also not
> specify the nnml-directory server parameter?
Whee. Until recently, we wouldn't have had to worry, since "/" was
forbidden in group names. But now there is IMAP and now "/" in group
names is possible.
Ick.
>> But there is a problem with the old .newsrc.eld files. Using the old
>> file with the new directory is going to be a problem,
>
> How so?
Because the new directory is empty (initially).
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
next prev parent reply other threads:[~2001-11-22 9:16 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 [this message]
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=vaf6683i2sl.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).