From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-10439-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 7997 invoked from network); 3 Apr 2000 23:10:19 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 3 Apr 2000 23:10:19 -0000
Received: (qmail 29194 invoked by alias); 3 Apr 2000 23:10:13 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 10439
Received: (qmail 29187 invoked from network); 3 Apr 2000 23:10:13 -0000
Date: Tue, 4 Apr 2000 01:09:29 +0200 (MET DST)
From: =?ISO-8859-1?Q?Johan_Sundstr=F6m?= <johsu650@student.liu.se>
X-Sender: johsu650@astmatix.ida.liu.se
To: zsh-workers@sunsite.auc.dk
Subject: <n> == <n->?
Message-ID: <Pine.GSO.4.02.10004040058110.14057-100000@astmatix.ida.liu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi!

When upgrading from zsh 3.1.6 to 3.1.6-dev-17 (as found in the Mandrake
zsh-3.1.6dev17-1mdk rpm), I was sad to notice that the glob behaviour of
the pattern <number> had changed to something identical to what I had
earlier (and still can) specified as <number->, that is, an open range of
numbers, from number onwards.

The old behaviour is, luckily, still available as <n-n> (although with
some extra pointless repetitive typing), but I rather liked the syntactic
simplicity of <n>, especially since <-n> or <n-> both are easy typers and
good for their purposes. <n> isn't useless, if (s)he who changed its=20
behaviour thought so, since it matches all the number n with any amount of
leading zeroes, a feature I have daily use for, when rummaging through
huge log directories, for instance.

Is this behaviour still there in the cvs version? On purpose? Any chance
of getting back the old style "syntactic sugar" pattern look?

/Johan Sundstr=F6m, occational zsh developer, frequent zsh user and deploye=
r