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.
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?
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?
--
was ist los? bist du krank?
PGP signature
