From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14466 invoked from network); 9 Apr 2002 18:09:25 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 9 Apr 2002 18:09:25 -0000 Received: (qmail 20186 invoked by alias); 9 Apr 2002 18:09:18 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16954 Received: (qmail 20172 invoked from network); 9 Apr 2002 18:09:16 -0000 From: "Bart Schaefer" Message-Id: <1020409180904.ZM3679@candle.brasslantern.com> Date: Tue, 9 Apr 2002 18:09:04 +0000 In-Reply-To: <24213.1018370734@csr.com> Comments: In reply to Peter Stephenson "Re: Zsh 3 and ${1+"$@"} (Was: [GNU Autoconf 2.53] testsuite.log: 126 failures)" (Apr 9, 5:45pm) References: <24213.1018370734@csr.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Peter Stephenson , zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Zsh 3 and ${1+"$@"} (Was: [GNU Autoconf 2.53] testsuite.log: 126 failures) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 9, 5:45pm, Peter Stephenson wrote: } } > Re-read the comment: "this leaves the unquoted substrings unsplit." If } > you turn off spbreak there, then ${=1+some words here} becomes broken. } } No, it doesn't, because that uses (spbreak = 2), hence the test. Sorry, I was writing in shorthand for: setopt shwordsplit for x in ${1-some words here}; do echo $x; done It's not sufficient just to twaddle spbreak -- it's necessary to actually parse the string and interpret quoting, but I think by the time multsub is done the quotes have already been stripped out. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net