From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12755 invoked by alias); 23 Feb 2018 18:21:29 -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: 42393 Received: (qmail 28745 invoked by uid 1010); 23 Feb 2018 18:21:29 -0000 X-Qmail-Scanner-Diagnostics: from mail-pf0-f178.google.com 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(209.85.192.178):SA:0(-1.9/5.0):. Processed in 1.123506 secs); 23 Feb 2018 18:21:29 -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, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: willrandship@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=QO85ZDKGSlNoSwJTC4+liprdryQFlsc//nnRwlImMP0=; b=k8aQC5E43VrKpwTtkj2UH1oj/8yAOCwShOBWCZ7KwvROxo3PKS2zkP/3l70Vc0rxwF O0VRaA7HyF8XMUPymkOENXOR46aq9agOkJb1g2ysjbiZwjhXl1v3X/1U9wrik+Zt8wM1 j7wslZ7HIehFlebBYWrx5ID86kIWBNDI39l0DVQlMRgRQMI80wDC9JfIz7hiRVrCTYFF 1gd+ZkCvD4Wu+JeDjxQy9Ggpu4IuBocNzrap1FEDOUX0GEpazgTwl2x3wQl4IhQMCzR9 n4ZnOjaQblqXjrfyz4938iyOv5/TRsLTmR+CMIPPvpMUVUQUl26GqCpFSzGkoCbNvO70 xCBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QO85ZDKGSlNoSwJTC4+liprdryQFlsc//nnRwlImMP0=; b=jvek0tNjZu+scyabPpVkZ+MJXgpOa2aq93S5EvW4vZ3piIWOOOD6LbN1eaTDhcRGsz DRdum3OC8qeS2q0eoTU/Cwi9mBXKeLwSnGCOxpsNydrCVX8Pi8c2Dpk4lAr/rI/SdVkE 0nRGH2NGUns/GPlEukKqyYn45ITnaMq0t+WJKsnDZkthwhFV6XYpasMc5Qf7RJwnGA8n zapIuvI10RyLX/jGMUqC0ey3Ubi4KNLeQKlj1Q5fOWhvHyL+COXD1vveoz7WyiUCxM93 S9tYmKLL4JRBSqoWdqWzmHKLb01heOYPReiZ3t+4IIziROtY4Ru/SfmyFZkneob1sjYM Ydbg== X-Gm-Message-State: APf1xPC/JGvlryd8q/ZxygzQc6QDP2ZsH8dnFIqGxcsKtGb0cEFwAjrI tuEqfx9Bm75+UOFJAJHZW7DuqPwQlqOqfqwhHwpWmH9c X-Google-Smtp-Source: AH8x226dn1/DxhG6CemwT7YAi+Rkl0G2jubM0yfPQ52NzcJzYRNzFzw4Qn/aclFSwwju/+J/0cb0qAdG3OStjCceIQw= X-Received: by 10.99.103.133 with SMTP id b127mr2077949pgc.155.1519410084810; Fri, 23 Feb 2018 10:21:24 -0800 (PST) MIME-Version: 1.0 From: William Shipley Date: Fri, 23 Feb 2018 11:21:24 -0700 Message-ID: Subject: Empty file execution behavior differs between zsh and sh To: zsh-workers@zsh.org Content-Type: multipart/alternative; boundary="001a114fd5285f94520565e53a42" --001a114fd5285f94520565e53a42 Content-Type: text/plain; charset="UTF-8" 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. --001a114fd5285f94520565e53a42--