From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14002 invoked from network); 25 Aug 1999 15:04:47 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Aug 1999 15:04:47 -0000 Received: (qmail 2758 invoked by alias); 25 Aug 1999 15:04:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7483 Received: (qmail 2750 invoked from network); 25 Aug 1999 15:04:30 -0000 From: "Bart Schaefer" Message-Id: <990825150416.ZM24557@candle.brasslantern.com> Date: Wed, 25 Aug 1999 15:04:15 +0000 In-Reply-To: <199908251420.QAA13906@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "PATCH: Re: Files modified after a given date" (Aug 25, 4:20pm) References: <199908251420.QAA13906@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: Re: Files modified after a given date MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Aug 25, 4:20pm, Sven Wischnowsky wrote: } Subject: PATCH: Re: Files modified after a given date } } } Zefram wrote: } > That's one of the many things I never got round to. I was going to } > have patterns like "*(F:func:)" call the shell function "func" with the } > name of each file which otherwise matches the glob pattern } } [...] it also allows one to give additional arguments as in } `*(F:func::arg1::arg2:)' and so on -- these are available as `$2' } etc. in the function. And finally it allows the function to say *what* } should be included by setting the `reply' or `REPLY' parameter to a } string or array (`REPLY' is only tested for a string value). } } (Maybe this is going a bit too far?) I don't have a problem with using reply/REPLY, but I think supplying additional arguments inside the glob qualifier is a bit excessive (and also accounts for most of the size of this patch, no?). -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com