From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: compctl whitespace changes
Date: Fri, 10 Aug 2001 15:56:30 +0000 [thread overview]
Message-ID: <1010810155631.ZM2266@candle.brasslantern.com> (raw)
In-Reply-To: <20010810105942.A5170@globnix.org>
On Aug 10, 10:59am, Phil Pennock wrote:
} Subject: Re: compctl whitespace changes
}
} On 2001-08-09 at 03:07 -0700, Will Yardley wrote:
} > I think it's created by a POP or IMAP client usually.
}
} Yeah. It's all because IMAP uses dot as a hierarchy separator.
IMAP can use almost anything it likes as a hierarchy separator. Don't
make claims for the whole protocol based on the courier implementation.
It is also notorious for taking assorted liberties with the protocol
that most of the other IMAP server writers are unhappy about.
} But enough people are using them that it makes sense for zsh to
} understand it.
I have a certain ambivalence about this, having worked on both email
clients and IMAP servers. If the file structure is being created by a
local delivery agent for use by an IMAP server, then it's that server
(or a local user agent designed to work with the same structure) that
should interpret the folder names, not your shell.
Suppose Company.Management decides to change to the Cyrus server. Then
all your mail files will disappear and you'll have a database interface
to deal with. A lot of people use that, too -- probably a lot more than
use Courier IMAP. That's not, by itself, a reason.
If your mail system uses ordinary files and leaves you in complete control
of what they're named and where to put them, then it makes sense for the
shell to understand it, because obviously the designers of the mail system
*intended* other programs to understand it.
Nevertheless, if someone can actually find me a reasonable description of
"Maildir++" (the description on the courier pages didn't say anything
about hierarchy, for example) I'll think about how _mailboxes might be
adjusted to cope with it.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-08-10 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 10:07 Will Yardley
2001-08-10 8:59 ` Phil Pennock
2001-08-10 15:56 ` Bart Schaefer [this message]
2001-08-10 16:36 ` Phil Pennock
2001-08-10 18:51 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 23:57 Phil Pennock
2001-08-08 8:22 ` Sven Wischnowsky
2001-08-08 16:03 ` Bart Schaefer
2001-08-09 6:14 ` Phil Pennock
2001-08-09 9:27 ` Bart Schaefer
2001-08-09 9:43 ` Phil Pennock
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=1010810155631.ZM2266@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).