From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19900 invoked from network); 28 Apr 2000 09:07:55 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 28 Apr 2000 09:07:55 -0000 Received: (qmail 28209 invoked by alias); 28 Apr 2000 09:07:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10997 Received: (qmail 28200 invoked from network); 28 Apr 2000 09:07:45 -0000 Date: Fri, 28 Apr 2000 10:06:03 +0100 From: Peter Stephenson Subject: Re: globbing bug, 3.0.6 In-reply-to: "Your message of Fri, 28 Apr 2000 01:01:53 -0000." <1000428010153.ZM21628@candle.brasslantern.com> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FTP00F90YM25M@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT > I don't want to change this in 3.0.8 unless it's also changing in 3.1.7 > or soon thereafter. What's the verdict on this one, folks? Apparently > bash behaves as zsh does now, but that's not a conclusive argument. I hesitate to reply, since I seem to be missing something, but as far as I'm concerned, zsh 3.1.7 just uses straightforward character range comparisons (not POSIX collation) with ordinary ranges such as [A-Z], but uses whatever the system tells it with special classes such as [[:upper:]] (this comes straight from ctype, not the zsh type macros), and this has been the case for the past couple of versions. Does anyone have evidence to the contrary? Barring a new option, is that the best default behaviour? Does anyone want an option POSIX_RANGES to restore full POSIX behaviour, despite the drawbacks? -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070