Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: nnimap subfolder problem
Date: Tue, 16 Oct 2001 14:35:19 +0200	[thread overview]
Message-ID: <iluelo3n4oo.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <vqon12reqsq.fsf@olan.imag.fr> (Nicolas KOWALSKI's message of "Tue, 16 Oct 2001 14:02:29 +0200")

Nicolas KOWALSKI <Nicolas.Kowalski@imag.fr> writes:

>>> PS 2: when I use nnml or nnfolder backends, Gnus stores groups using
>>> subdirectories for group names like "foo.bar.geez" (gives
>>> foo/bar/geez). Is it possible to use the same functionnality for
>>> nnimap backend ?
>> 
>> I don't think so, it would mean making `.' and `/' equivalent, and
>> that is something the IMAP server should do (if at all).
> 
> I disagree : what happens if our Eudora/Messenger/Outlook users
> create folders containing dot in their names ? The Gnus beahviour to
> create subfolders with dot-named folders is Gnus specific, ans
> should stays IMHO as is.

But with nnimap, the directories and files exists on the server, so
Gnus has no control of how they are named other than by replacing `.'
with `/' in the group name but that would be confusing, I think.

I think everything would work fine if you create a group with a dot in
its name using another client (I do this all the time).  What problems
do you see?

Or were you talking about the NOV cache?  It could translate `.' into
`/' but I don't see the point, there would only be one file in most
directories anyway, wouldn't it?

Translating `.' into `/' is only something you need if your filesystem
is 8+3 or similar and can't store e.g. "foo.bar.baz", isn't it?  I
haven't seen any IMAP server that has this problem.




  reply	other threads:[~2001-10-16 12:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 11:13 Nicolas KOWALSKI
2001-10-16 11:41 ` Simon Josefsson
2001-10-16 12:02   ` Nicolas KOWALSKI
2001-10-16 12:35     ` Simon Josefsson [this message]
2001-10-16 13:04       ` Nicolas KOWALSKI
2001-10-16 13:32         ` Simon Josefsson
2001-10-16 13:46           ` Kai Großjohann
2001-10-16 14:01             ` Nicolas KOWALSKI
2001-10-16 18:12             ` Simon Josefsson
2001-10-17  4:27               ` Amos Gouaux
2001-10-16 13:59           ` Nicolas KOWALSKI
2001-10-16 18:27 ` Steinar Bang
2001-12-04 23:48 Kevin Hilman
2001-12-07 14:26 ` Simon Josefsson
2001-12-07 17:23   ` Kevin Hilman
2001-12-07 19:29     ` Simon Josefsson
2001-12-10 19:48       ` Kevin Hilman

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=iluelo3n4oo.fsf@barbar.josefsson.org \
    --to=jas@extundo.com \
    --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).