Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: /bin/zsh -ce 'false; echo bug'

X-seq: zsh-workers 7508
From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
To: "Owen M. Astley" <oma1000@xxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
Subject: Re: /bin/zsh -ce 'false; echo bug'
Date: Thu, 26 Aug 1999 18:06:18 +0000
In-reply-to: <Pine.OSF.3.96.990826091939.27810A-100000@xxxxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
References: <Pine.OSF.3.96.990826091939.27810A-100000@xxxxxxxxxxxxxxxxxxxxxxxxx>

On Aug 26,  9:26am, Owen M. Astley wrote:
> Subject: Re: /bin/zsh -ce 'false; echo bug'
> On Wed, 25 Aug 1999, Matt Watson wrote:
> 
> > gnumake-3.74 wants to use "/bin/sh -ce <commandstring>" to exec a sub  
> > make. Unfortunately if zsh == sh, zsh doesn't grok the -ce as separate  
> > options, so it ignores the "e" and does not set ERREXIT.
> 
> I 'think' that POSIX doesn't allow for options of this type, it should be
> written as -c -e <commandstring>.

Zsh interprets everything after the -c as part of the command, so that will
attempt to run a command named "-e".  If it really is the case that the
order of option letters doesn't matter (which appears to be true of bash,
at least), then zsh's option parser needs a bit more of a workover.

Follow-Ups:
- PATCH: Re: /bin/zsh -ce 'false; echo bug'
  - From: Bart Schaefer

References:
- Re: /bin/zsh -ce 'false; echo bug'
  - From: Owen M. Astley

Messages sorted by: Reverse Date, Date, Thread, Author