From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25444 invoked from network); 27 Nov 2005 18:41:00 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.0 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 27 Nov 2005 18:41:00 -0000 Received: (qmail 97843 invoked from network); 27 Nov 2005 18:40:54 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 27 Nov 2005 18:40:54 -0000 Received: (qmail 15157 invoked by alias); 27 Nov 2005 18:40:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 22041 Received: (qmail 15147 invoked from network); 27 Nov 2005 18:40:52 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 27 Nov 2005 18:40:52 -0000 Received: (qmail 97566 invoked from network); 27 Nov 2005 18:40:52 -0000 Received: from vms042pub.verizon.net (206.46.252.42) by a.mx.sunsite.dk with SMTP; 27 Nov 2005 18:40:51 -0000 Received: from candle.brasslantern.com ([71.116.81.225]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQM000SNMK1O2G0@vms042.mailsrvcs.net> for zsh-workers@sunsite.dk; Sun, 27 Nov 2005 12:40:50 -0600 (CST) Received: from candle.brasslantern.com (IDENT:schaefer@localhost [127.0.0.1]) by candle.brasslantern.com (8.12.11/8.12.11) with ESMTP id jARIemVn007961 for ; Sun, 27 Nov 2005 10:40:48 -0800 Received: (from schaefer@localhost) by candle.brasslantern.com (8.12.11/8.12.11/Submit) id jARIemOp007960 for zsh-workers@sunsite.dk; Sun, 27 Nov 2005 10:40:48 -0800 Date: Sun, 27 Nov 2005 18:40:48 +0000 From: Bart Schaefer Subject: Re: path and += troubles In-reply-to: <200511271334.jARDYWrO004473@pwslaptop.csr.com> To: zsh-workers@sunsite.dk Message-id: <1051127184048.ZM7959@candle.brasslantern.com> MIME-version: 1.0 X-Mailer: Z-Mail (5.0.0 30July97) Content-type: text/plain; charset=us-ascii References: <200511271334.jARDYWrO004473@pwslaptop.csr.com> Comments: In reply to Peter Stephenson "Re: path and += troubles" (Nov 27, 1:34pm) On Nov 27, 1:34pm, Peter Stephenson wrote: } Subject: Re: path and += troubles } } > schaefer<508> echo $1+=($2) } > zsh: no match } > schaefer<509> $1+=($2) } > schaefer<510> } > } > Where's my "no match" error in the second case? } } I'm having a hard time coming up with a combination of options and } arguments that does this. Starting from "zsh -f": zagzig% setopt cshnullglob zagzig% echo $1+=($2) zsh: no match zagzig% $1+=($2) zagzig% The problem of course is that cshnullglob is supposed to be like nomatch if *nothing* matches -- it's only supposed to be like nullglob if at least one of several patterns matches. } But didn't you say the problem was with NULLGLOB? I originally [in the -users thread] mentioned that the error message vanishes with either nullglob or cshnullglob. After I figured out that it happens because the test string I was using was somehow a valid glob qualifier -- that is, "(2)" is a valid qualifier, though I have no idea what meaning it can possibly have -- then I said [on -workers] that it was limited to cshnullglob.