From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8614 invoked from network); 19 Apr 2001 07:05:55 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Apr 2001 07:05:55 -0000 Received: (qmail 24144 invoked by alias); 19 Apr 2001 07:05:43 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14022 Received: (qmail 24132 invoked from network); 19 Apr 2001 07:05:43 -0000 From: Sven Wischnowsky Date: Thu, 19 Apr 2001 09:05:36 +0200 (MET DST) Message-Id: <200104190705.JAA10878@beta.informatik.hu-berlin.de> To: zsh-workers@sunsite.dk Subject: Re: PATCH: Assorted parameter stuff In-Reply-To: <1010419035736.ZM9073@candle.brasslantern.com> Bart Schaefer wrote: > ... > > Well, it's not as straightforward as I thought -- the parse gets tangled > up the with parsing of [[ ... ]], among other things -- I feared that... > and I just noticed > that you can get the equivalent effect by surrounding the whole thing with > braces: > > % foo='any random string' > % echo ${foo[(i)dom str]} > 8 > > So I think I'm going to leave it at 14008+14016 unless somebody comes up > with other bugs to zap. [Blink, hm, why didn't I know that?...] 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 may be other complicated subscripts in the completion code that can serve as good tests, but none of the other completion functions I tried failed and grepping for `complicated subscripts' isn't exactly easy. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de