From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24157 invoked from network); 3 Jun 1999 12:03:04 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 Jun 1999 12:03:04 -0000 Received: (qmail 17803 invoked by alias); 3 Jun 1999 12:02:56 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6448 Received: (qmail 17796 invoked from network); 3 Jun 1999 12:02:55 -0000 Date: Thu, 3 Jun 1999 08:02:51 -0400 From: Clint Adams To: Bart Schaefer Cc: zsh-workers@sunsite.auc.dk Subject: Re: MAIL, MAILPATH and maildir support Message-ID: <19990603080251.A31258@dman.com> References: <19990603000030.A20027@dman.com> <990603054646.ZM2687@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <990603054646.ZM2687@candle.brasslantern.com>; from Bart Schaefer on Thu, Jun 03, 1999 at 05:46:46AM +0000 > I was about to gripe about how horribly inefficient this bit of code is, > when I realized I'd forgotten that the existing support for directories > is if anything worse. Recursively stat() an entire directory tree?? > Does anyone really make use of this feature? Yes, people use this. > Regardless of efficiency, I think it's a bad idea to start including > support for specific mail delivery formats in the shell. It's one thing > to get the standard system information about a file and report that the > file has changed; it's quite another to have knowledge of the internals > of the file format. Well, it's MAILPATH, not GENERICFILEPATH. There are a limited number of mailbox formats that pose significance to the shell. > Perhaps checkmailpath is a candidate for some kind of loadable module ... Fair enough.