Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: parameter and quoting (was: Re: Completion problems.)
- X-seq: zsh-workers 7376
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: parameter and quoting (was: Re: Completion problems.)
- Date: Thu, 5 Aug 1999 14:53:10 +0200 (MET DST)
- In-reply-to: Peter Stephenson's message of Thu, 05 Aug 1999 14:05:14 +0200
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Peter Stephenson wrote:
> Sven Wischnowsky wrote:
> > 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.
Ah, right, hadn't thought about patterns (ahem)... "${a%'}" reports
the error.
Hm. Should the proposed new flag apply to those, too, and change the
current behaviour to not report the error or should the current
behaviour of (Q) be changed?
Personally I prefer the first one, but that would require an
incompatible change. (And making the flag turn off errors for
${...%...} and friends and turn it on for (Q) is almost certainly the
wrong way).
Bye
Sven
--
Sven Wischnowsky wischnow@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author