From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14149 invoked from network); 31 Dec 1997 21:53:15 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 31 Dec 1997 21:53:15 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id QAA08791; Wed, 31 Dec 1997 16:37:09 -0500 (EST) Resent-Date: Wed, 31 Dec 1997 16:37:09 -0500 (EST) Date: Wed, 31 Dec 1997 22:37:52 +0100 (MET) From: Wessel Dankers X-Sender: wsl@telamon.dyn.ml.org Reply-To: Wessel Dankers To: Geoff Wing cc: zsh-workers@math.gatech.edu Subject: Re: <..> ranges in globbing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"LZcQp.0.F92.4ihgq"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3664 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On 31 Dec 1997, Geoff Wing wrote: > Heyla, > % touch 101 111 121 > % ls <10-12>1 > ls: <10-12>1: No such file or directory > Now, it's obvious why it's failing, since 101, 111 & 121 don't match the > 10 to 12 range. My opinion is that it probably shouldn't fail in this case, Indeed. Any glob experts around? > but maybe a different operator or option/modifier should be used to get it > to match. since there may be cases where someone wants to match on, say, > ``<1-50>foo'' and not get, say, ``100foo'' matching. <1-50>foo would never match 100foo, even with the behaviour described above. Even though "<1-50>" could expand to `10', it still leaves an unexplained `0'. "<1-50>foo" != "<1-50>0foo", so there is no need for an extra operator. -- Wessel Dankers