From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5923 invoked from network); 4 May 2000 15:56:57 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 4 May 2000 15:56:57 -0000 Received: (qmail 25962 invoked by alias); 4 May 2000 15:56:39 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11160 Received: (qmail 25951 invoked from network); 4 May 2000 15:56:38 -0000 Date: Thu, 04 May 2000 16:56:05 +0100 From: Peter Stephenson Subject: Re: Let's do it RE: Should we backup this change? RE: Modifier substitutions. In-reply-to: "Your message of Thu, 04 May 2000 11:02:35 +0400." <000501bfb596$b9e75290$21c9ca95@mow.siemens.ru> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FU100IKILLHRZ@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT > > The change went in in 6002. It was followed in 6003 by a > > change to allow > > a leading double backslash to escape the delimiter. So all > > you need to > > do is change uses of ${foo/$bar/...} into ${foo/\\$bar/...} > > to avoid the > > confusion. > > Unfortunately, it is so inconsistent, that I really suggest to backup > it. I'm quite happy to remove it which is easy. Currently there's no simple replacement in the case of _configure, however, because (#s) doesn't get tokenized (the `#' didn't need to be, it was always recognised, hence the need for quoting). This would require the -s option to _arguments to do some kind of globsubst thing, which may or may not be desirable. I haven't looked for any other uses of this feature. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070