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

Re: Empty file execution behavior differs between zsh and sh

X-seq: zsh-workers 42394
From: Eric Cook <llua@xxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: Empty file execution behavior differs between zsh and sh
Date: Fri, 23 Feb 2018 16:59:06 -0500
In-reply-to: <CAFYD1PrHbgk14SwMkhtyxB9O-6P1mSAw2zVmDNevQuVWjDX+KQ@mail.gmail.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <CAFYD1PrHbgk14SwMkhtyxB9O-6P1mSAw2zVmDNevQuVWjDX+KQ@mail.gmail.com>

On 02/23/2018 01:21 PM, William Shipley wrote:
> In sh and bash
> 
> touch true
> chmod +x true
> ./true
> echo $?
> 
> prints 0, as an empty file returns successfully on execution.
> 
> On zsh, the same command returns
> 
> zsh: exec format error: ./true
> 
> on stderr and
> 
> 126
> 
> for the echo statement.
> 
> This holds true when running zsh in sh compatibility mode:
> 
> ARGV0=sh zsh
> 
> I don't consider this of pressing importance, but it would be one step
> closer to sh compatibility.
> 

for more context why this was probably reported:
https://twitter.com/rob_pike/status/966896123548872705

References:
- Empty file execution behavior differs between zsh and sh
  - From: William Shipley

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