From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20550 invoked from network); 1 Jun 1999 10:39:58 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Jun 1999 10:39:58 -0000 Received: (qmail 17971 invoked by alias); 1 Jun 1999 10:39:47 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6418 Received: (qmail 17963 invoked from network); 1 Jun 1999 10:39:47 -0000 Date: Tue, 1 Jun 1999 12:39:44 +0200 (MET DST) Message-Id: <199906011039.MAA25089@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Tue, 1 Jun 1999 10:04:54 +0000 Subject: Re: pws-20 parameter completion can't handle new syntax Bart Schaefer wrote: > 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'. I don't see a better solution without also dealing with the other quoting-trouble and I have both of them together in my todo-list, so no need to fear... > Hmm, perhaps it's time to actually set up a bug tracking system for zsh. Yes, maybe. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de