From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18132 invoked from network); 11 Feb 1999 18:40:17 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 11 Feb 1999 18:40:17 -0000 Received: (qmail 14696 invoked by alias); 11 Feb 1999 18:39:49 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5346 Received: (qmail 14685 invoked from network); 11 Feb 1999 18:39:35 -0000 From: "Bart Schaefer" Message-Id: <990211103925.ZM3661@candle.brasslantern.com> Date: Thu, 11 Feb 1999 10:39:25 -0800 In-Reply-To: <9902111708.AA58097@ibmth.df.unipi.it> Comments: In reply to Peter Stephenson "Re: Tar file and Re: Bad interaction between -iprefix and -string" (Feb 11, 6:08pm) References: <9902111708.AA58097@ibmth.df.unipi.it> X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@sunsite.auc.dk Subject: Re: Tar file and Re: Bad interaction between -iprefix and -string MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 11, 6:08pm, Peter Stephenson wrote: } Subject: Re: Tar file and Re: Bad interaction between -iprefix and -string } } [...] for some reason } } for i in "$patcomps[@]"; do } } was being called when patcomps was empty (should it really do that?) Hmm. You mean the for loop, looped? Obviously it shouldn't do that. How was patcomps initialized up to that point? } > - I also added support for Peter-like (sorry ;-) special completion } > keys, see the comment in `init' } } I think this could be a bit neater: in the patch, the widget defined } now has the same name as the file with the #key-array or #key-function } in it. This was easy, it just needed $keycomps to be an assoc array. This is all getting amazingly perl-ish. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com