From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20333 invoked from network); 1 Jun 1999 10:05:26 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Jun 1999 10:05:26 -0000 Received: (qmail 15582 invoked by alias); 1 Jun 1999 10:05:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6415 Received: (qmail 15556 invoked from network); 1 Jun 1999 10:04:59 -0000 From: "Bart Schaefer" Message-Id: <990601100454.ZM10030@candle.brasslantern.com> Date: Tue, 1 Jun 1999 10:04:54 +0000 In-Reply-To: <199906010930.LAA24609@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: pws-20 parameter completion can't handle new syntax" (Jun 1, 11:30am) References: <199906010930.LAA24609@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: pws-20 parameter completion can't handle new syntax MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 1, 11:30am, Sven Wischnowsky wrote: } Subject: Re: pws-20 parameter completion can't handle new syntax } } > zagzig% echo ${"comp } > } } Hm, yes. The patch below makes this work, but it also makes `${ comp' } work, because check_param() gets the string in a form where the quote } is replaced by a space. I think I'd prefer this particular "fix" were left out. We're more likely to notice that `${"foo' still needs fixing than we are to remember to un-fix `${ foo'. Hmm, perhaps it's time to actually set up a bug tracking system for zsh. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com