From: Phil Pennock <Phil.Pennock@globnix.org>
To: zsh-users@sunsite.dk
Subject: Re: compctl whitespace changes
Date: Thu, 9 Aug 2001 11:43:31 +0200 [thread overview]
Message-ID: <20010809114331.A19434@globnix.org> (raw)
In-Reply-To: <1010809092756.ZM899@candle.brasslantern.com>; from schaefer@brasslantern.com on Thu, Aug 09, 2001 at 09:27:56AM +0000
On 2001-08-09 at 09:27 +0000, Bart Schaefer wrote:
> } With Maildir, you have your main Maildir, eg ~/Maildir/, and you can
> } have folders inside that, each of which has a name starting with a
> } period. The normal one is .Trash, but others can be created.
>
> Are you sure about this? There's nothing in the maildir "spec" about
> the format of the directory names, only their contents, and nothing in
> the mutt documentation either that would indicate why every folder name
> would be hidden with a leading dot. I'd expect ".Trash" to be a special
> (deliberately invisible) folder where deleted messages are moved before
> purging.
Mutt's Maildir support is minimal. Not a good example.
I should've been more explicit and said Maildir++, which most software
aside from Dan Bernstein's uses, for various reasons. It's a superset.
Example documentation:
<http://www.courier-mta.org/maildirmake.html>
Something a quick google throws up:
<http://www.exim.org/pipermail/exim-users/Week-of-Mon-20000103/015916.html>
which in passing demonstrates this being used.
> } Do people feel that a supplied patch to add Maildir support into
> } $mailpath would be appropriate? I'm happy to do the work, if it's not
> } considered a bad idea.
>
> It's already there. "configure --enable-maildir-support ..."
*sigh* Thank you. I did check the run-time docs. And I just
double-checked:
~/zsh-4.0.2/Doc%; fgrep -i maildir **/*.yo
Zsh/compctl.yo:example(compctl -/ -W ~/Mail maildirs)
Further, the entry for $mailpath in zshparam(1) is a little misleading,
as it makes explicit reference to what happens when an entry is a
directory:
If an element is a directory instead of a
file the shell will recursively check every file in
every subdirectory of the element.
I'll just go rebuild zsh ... (serves me right for using *BSD Ports)
Thanks,
--
PHB: It needs to be so easy that your mother could use it.
Dilbert: My mother isn't a moron. Maybe we could use your mother as a test.
PHB: What makes you think my mother is a moron?
Dilbert: She fed you.
next prev parent reply other threads:[~2001-08-09 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-08-09 10:07 Will Yardley
2001-08-10 8:59 ` Phil Pennock
2001-08-10 15:56 ` Bart Schaefer
2001-08-10 16:36 ` Phil Pennock
2001-08-10 18:51 ` Bart Schaefer
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=20010809114331.A19434@globnix.org \
--to=phil.pennock@globnix.org \
--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).