From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23355 invoked from network); 5 Aug 1999 12:36:32 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 Aug 1999 12:36:32 -0000 Received: (qmail 25845 invoked by alias); 5 Aug 1999 12:36:19 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7375 Received: (qmail 25837 invoked from network); 5 Aug 1999 12:36:16 -0000 Message-Id: <9908051205.AA36102@ibmth.df.unipi.it> To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: parameter and quoting (was: Re: Completion problems.) In-Reply-To: "Sven Wischnowsky"'s message of "Thu, 05 Aug 1999 14:19:00 DFT." <199908051219.OAA16988@beta.informatik.hu-berlin.de> Date: Thu, 05 Aug 1999 14:05:14 +0200 From: Peter Stephenson Sven Wischnowsky wrote: > This is the solution that makes errors be ignored, because I have to > ask first: we could easily add another flag that turns on error- > checking. OR should error-reporting be the normal case and we should > have a flag to turn it off? For modifiers we could have a new modifier > that can be combined with `Q' a la `g' and `f', e.g. `$a:EQ' or > something like that. And with respect to the flag: this could be made > to work for things like `${...%...}', too. Since this is mainly for parameters, it might be better just to alter the version with flags. Probably it shouldn't report an error normally. > Btw. something like `${foo%(}' > currently gives me a non-zero return status but no error message -- > even though there seems to be some extra code for it -- I haven't > investigated any firther yet, but this seems wrong, doesn't it? The behaviour of BAD_PATTERN is a bit inconsistent: sometimes the option is respected, sometimes it isn't, sometimes bad patterns aren't reported at all. There's probably quite a lot wrong. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy