From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14947 invoked from network); 8 Jun 1999 14:52:09 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 8 Jun 1999 14:52:09 -0000 Received: (qmail 12317 invoked by alias); 8 Jun 1999 14:51:56 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6529 Received: (qmail 12289 invoked from network); 8 Jun 1999 14:51:49 -0000 From: "Bart Schaefer" Message-Id: <990608145140.ZM24078@candle.brasslantern.com> Date: Tue, 8 Jun 1999 14:51:40 +0000 In-Reply-To: <9906081206.AA21204@ibmth.df.unipi.it> Comments: In reply to Peter Stephenson "PATCH: pws-21: parentheses in command word" (Jun 8, 2:06pm) References: <9906081206.AA21204@ibmth.df.unipi.it> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Subject: Re: PATCH: pws-21: parentheses in command word MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 8, 2:06pm, Peter Stephenson wrote: } Subject: PATCH: pws-21: parentheses in command word } } I mentioned this a while ago, but can't find that in the archive, because I } can never find things. I frequently do searches that I *know* should succeed, but that find nothing. I suppose I should send a couple of them off to Geoff and ask why. } For some reason, parentheses are treated specially in the command word in } zsh, not just at the start (where, of course, they start a subshell). I think know why, but perhaps now the lexer is more sophisticated. I have an early-morning meeting today, so I don't have time to build pws-21 and try the patch. They're treated that way because array assignments are in command position. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com