From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9621 invoked from network); 19 Apr 2001 09:21:07 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Apr 2001 09:21:07 -0000 Received: (qmail 23746 invoked by alias); 19 Apr 2001 09:21:00 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14025 Received: (qmail 23729 invoked from network); 19 Apr 2001 09:20:59 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) Date: Thu, 19 Apr 2001 13:20:50 +0400 (MSD) From: Andrej Borsenkow X-X-Sender: To: Subject: Re: PATCH: Assorted parameter stuff In-Reply-To: <200104190705.JAA10878@beta.informatik.hu-berlin.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 19 Apr 2001, Sven Wischnowsky wrote: > > > Anyway, about 14008: I only found one problem with a complicated > subscript in _arguments, line 81, which can be seen by completing after > `./configure --'. 14016 doesn't seem to fix it either and I didn't > look closely enough to be able to say what exactly the problem is. > There seems to be a problem quoting open bracket: bor@localhost% foo=(a b c) bor@localhost% print -r "$foo[(I)\]]" bor@localhost% print -r "$foo[(I)[]" zsh: invalid subscript bor@localhost% print -r "$foo[(I)\[]" zsh: invalid subscript bor@localhost% print -r "$foo[(I)\\[]" zsh: invalid subscript bor@localhost% print -r "$foo[(I)\\\[]" zsh: invalid subscript bor@localhost% print -r "$foo[(I)\\\\[]" zsh: invalid subscript O.K. I think it already exceeds any reasonable number of backslashes :-) This is with both patches of Bart. 4.0.1-pre-1 is even more funnier ... bor@localhost% zsh-4.0.1-pre-1 bor@localhost% foo=(a b c) bor@localhost% print $foo[(I)\[] 0(I)[] so I ask myself if it ever worked -andrej