From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8125 invoked from network); 9 Oct 2007 14:46:44 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 9 Oct 2007 14:46:44 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 4286 invoked from network); 9 Oct 2007 14:46:39 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 9 Oct 2007 14:46:39 -0000 Received: (qmail 6899 invoked by alias); 9 Oct 2007 14:46:36 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 23928 Received: (qmail 6881 invoked from network); 9 Oct 2007 14:46:35 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 9 Oct 2007 14:46:35 -0000 Received: (qmail 3938 invoked from network); 9 Oct 2007 14:46:35 -0000 Received: from cluster-g.mailcontrol.com (85.115.41.190) by a.mx.sunsite.dk with SMTP; 9 Oct 2007 14:46:29 -0000 Received: from cameurexb01.EUROPE.ROOT.PRI ([62.189.241.200]) by rly09g.srv.mailcontrol.com (MailControl) with ESMTP id l99EkMee011524 for ; Tue, 9 Oct 2007 15:46:23 +0100 Received: from news01.csr.com ([10.103.143.38]) by cameurexb01.EUROPE.ROOT.PRI with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Oct 2007 15:46:21 +0100 Received: from news01.csr.com (localhost.localdomain [127.0.0.1]) by news01.csr.com (8.14.1/8.13.4) with ESMTP id l99EkMTb026512 for ; Tue, 9 Oct 2007 15:46:22 +0100 Received: from csr.com (pws@localhost) by news01.csr.com (8.14.1/8.14.1/Submit) with ESMTP id l99EkMXI026509 for ; Tue, 9 Oct 2007 15:46:22 +0100 Message-Id: <200710091446.l99EkMXI026509@news01.csr.com> X-Authentication-Warning: news01.csr.com: pws owned process doing -bs To: zsh-workers@sunsite.dk Subject: Re: bug in patterns used for filename expansion (e.g. a[b/c]d) In-reply-to: <20071009141239.GA10216@prunille.vinc17.org> References: <20071009124055.GH22340@prunille.vinc17.org> <200710091259.l99Cxifg025637@news01.csr.com> <20071009141239.GA10216@prunille.vinc17.org> Comments: In-reply-to Vincent Lefevre message dated "Tue, 09 Oct 2007 16:12:39 +0200." Date: Tue, 09 Oct 2007 15:46:21 +0100 From: Peter Stephenson X-OriginalArrivalTime: 09 Oct 2007 14:46:22.0010 (UTC) FILETIME=[28B679A0:01C80A83] X-Scanned-By: MailControl A-07-08-10 (www.mailcontrol.com) on 10.71.0.119 Vincent Lefevre wrote: > On 2007-10-09 13:59:44 +0100, Peter Stephenson wrote: > > As I said on the Austin group list, this isn't a bug. It's controlled > > by the option NOMATCH; you'll find that if zsh is in compatibility mode > > that option is unset. > > OK, but these compatibility modes are not really clear Yes, I tend to agree with that, although it's partly because the targets are moving and we haven't tried very hard to keep up. > e.g. which sh and which ksh? And what about POSIX? "sh" usually means POSIX with a leaning towards traditional behaviour where that's not in conflict with the spec. Anything in "sh" mode that's definitely in violation of POSIX can be regarded as a bug. (Whether it's going to get fixed is another matter, as with the long standing word-splitting niggle that Wayne eventually fixed.) "ksh" really means ksh88 and it probably ought to be documented as such. There have been vague plans to have more recent ksh features but they need architectural changes. pws