From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25602 invoked from network); 10 Apr 2000 08:11:35 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 10 Apr 2000 08:11:35 -0000 Received: (qmail 12055 invoked by alias); 10 Apr 2000 08:11:20 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10613 Received: (qmail 12045 invoked from network); 10 Apr 2000 08:11:19 -0000 Date: Mon, 10 Apr 2000 10:11:16 +0200 (MET DST) Message-Id: <200004100811.KAA31446@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Fri, 07 Apr 2000 21:05:12 +0100 Subject: Re: PATCH: Re: Tags again Peter Stephenson wrote: > Sven Wischnowsky wrote: > > Ok. Any questions left? ;-) > > Thanks for the explanation. I've upgraded my remarks in the user guide > (which actually already gave half the story) to say `don't use tag-order > with files'. > > I was still struck by one slight hickup: I expected to be able to say > '*.lst:globbed-files *(-/):directories' to get them named differently but > called at the same time, but it seems you have to do > '*.lst *(-/):globbed-files' which kind of defeats the object of giving them > a name. But maybe I've missed something again. I'm don't think it makes the name useless, but... hey, I hadn't thought of this multiple names in one string thing. Makes it look more like tag-order which is almost certainly a good thing. One small problem: we always supported (in file-patterns and in the argument to -g) multiple patterns separated by white space. If we find an acceptable syntax for this combined with the multiple-names thing, I'll implement it. Using backslashes before the spaces would be the wrong thing, though -- that's already used to include spaces in the patterns. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de