From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5416 invoked by alias); 23 Feb 2018 22:04:32 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 42394 Received: (qmail 25895 invoked by uid 1010); 23 Feb 2018 22:04:32 -0000 X-Qmail-Scanner-Diagnostics: from mout.gmx.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(212.227.15.18):SA:0(-1.9/5.0):. Processed in 10.501175 secs); 23 Feb 2018 22:04:32 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, SPF_PASS autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: llua@gmx.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Subject: Re: Empty file execution behavior differs between zsh and sh To: zsh-workers@zsh.org References: From: Eric Cook Message-ID: <3296a27c-2ea7-e7d9-a00a-bc1dbe75bf53@gmx.com> Date: Fri, 23 Feb 2018 16:59:06 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:jb10/sYNAOWeeEgw9SDhnDEZUrRMS0jj22UccLa38DskfLkgLPK RjPZAFXRzlEnfaXgIxWEbkIBEYfoCUtyeujPyo8cAoyqPEuPOctF5yGUNDTSbWfl6zjQAqh L/7tX0mEV3bRmngjrGdxAQ/C2Fj+eWTdSlqvKXO5RnEpZfGO4wkdw0YM7CgRL1P1Tr+0yK4 dcKmMKH0Sam43OOCPSt2Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:irqCTmShoXc=:hUDMjp2knypewaYema1bMJ q1Sb3zebB96my4t7h9n/k0hro3mqJsnk3IS0ZKE8h7CGDV+WVoXbu6JdqB2lrsKAbs30zqFYa MwHTeMehSCf7hd+WduN4RWO7G74QfG3CTTvZ94y+ZHW4l5a+lVtBKygpAlNS8cExodvbROkMt BN4ClB2ze+19VMee9LRvRx7eFY3QMHDN9KHK7lsnr3LUW5QG8zcjg4Ls/4kyd4zFZoKN+QBF9 AJvmTEDV4uZWMDPNTaXljg9qSob37EmqK5Z1+F0B9llDSdlP5vjhBxlQSrHiQsLEQu3ckheE6 dzWMBknSG2R/+MvWJfi3DqQYGqVXY/1PnXYE8eKTjx1WlG9VF+ie8ZkhP+s53gZ882TFX1XRK bm/sMHZ5ttUnxhCFIPkm9dnL1wl5/lhQ0LunyNYE+FOKNcMF6J+K3PnUzb9ffUGZ9uyY7+goT qNSjf+mr3tIHRyidSpipxn+fVjzxDHZMsAu8IfjkqQDOwWOkpRAAu/hTSlXJ//0zUJO/huOh8 g+df+UwTC7kku7c2TPhS0biYb641UH2RFzDtcTYnV0oy6DTF9E107TLmjtp0JWRNQT1KiB8Le xI/mpQGVTISFVja31PgeC81LA9IX+mEolRc0S+RqTNxyTdQCTeYqh4jejDYn6q9xiFGCB9eVU IpXEsixv4B7E2CSa3XZHG8qkoAiLcFfAREW+zBKm2DWzt/9uEzmZKRUt3zsSeb7zkM+6lfyn+ QKaaQV9PFaDbYHtj/BuxZ/S5d+5g6ssXOd5YyMqiYfWTOYW90/YvkCliyOdzZ1VeQUB1EOnGk KHv3/o0/N4yBHBXD+CDcJg1nNa50T48qUiBr2xxBh/MObXYoTI= 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