From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21437 invoked from network); 3 Jun 1999 05:50:27 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 Jun 1999 05:50:27 -0000 Received: (qmail 19721 invoked by alias); 3 Jun 1999 05:50:09 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6446 Received: (qmail 19714 invoked from network); 3 Jun 1999 05:50:05 -0000 From: "Bart Schaefer" Message-Id: <990603054646.ZM2687@candle.brasslantern.com> Date: Thu, 3 Jun 1999 05:46:46 +0000 In-Reply-To: <19990603000030.A20027@dman.com> Comments: In reply to Clint Adams "MAIL, MAILPATH and maildir support" (Jun 3, 12:00am) References: <19990603000030.A20027@dman.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Clint Adams , zsh-workers@sunsite.auc.dk Subject: Re: MAIL, MAILPATH and maildir support MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 3, 12:00am, Clint Adams wrote: } Subject: MAIL, MAILPATH and maildir support } } This patch is from Miquel van Smoorenburg . } } It corrects the treatment of maildir-format mailbox directories } in MAILPATH. 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? 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. Perhaps checkmailpath is a candidate for some kind of loadable module ... -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com