> Hi all,
>
> I've been taking a look at $imap_home_namespace, and I think it has
> some inconsistencies.
>
> Theoretically if you're using, say, UW-IMAP where your default root is
> your home directory but your mail is probably all in ~/Mail, you could
> set $imap_home_namespace=Mail, and $folder={host} and get what you
> want in the browser (namely, INBOX and the other namespaces, plus a
> list of the mailboxes in ~/Mail). But this doesn't work well with
> saving messages or changing folders, where you'd like to be able to do
> c (or s) =newmailbox. Currently even if $imap_home_namespace is set to
> Mail this will access ~/newmailbox, rather than ~/Mail/newmailbox.
You need to set folder={server}Mail in order for =newmailbox to go to the correct
location.
> Do we even need $imap_home_namespace? I'd figure it would be fine to
> just note when the folder we're currently browsing matches $folder,
> and add INBOX and the other namespaces to that view. I could see a
> problem with ../ (the parent folder) in that case:
>
> IMAP ../
> IMAP INBOX
> IMAP mbox1
> IMAP mbox2
> IMAP subfolder1/
> IMAP #sharedns1/
> IMAP #sharedns2.
>
> ie where does .. go, and what happens to the root namespaces there?
.. goes to the home directory and you then get a listing of the files there.
>
> On the other hand, I don't use this variable myself and never really
> knew what to do with it. Some users don't find it particularly useful
> as it stands now, so I'm thinking of changing it. Thoughts?
I don't see why imap_home_namespace should exist, if you are browsing the folder
directory then excluding .. and including INBOX should produce the correct result.
I tried imap_home_namespace because INBOX was not listed and the documentation
said to use it under those circumstances. Unfortunately the code in that area was
not easy to follow, so I could not work out what was intended.
---------------------------------------
Phil Chambers ([EMAIL PROTECTED])
University of Exeter
