From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18069 invoked by alias); 19 Dec 2016 19:14:42 -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: X-Seq: 40214 Received: (qmail 17381 invoked from network); 19 Dec 2016 19:14:42 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f181.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.217.181):SA:0(-0.0/5.0):. Processed in 0.964347 secs); 19 Dec 2016 19:14:42 -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=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.181 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=logomnGm2/Va7xXc4vABdcxpFzG/aRf9J+VKYcO0+8E=; b=YGTSw0h/Q3D1cvKU56yaUZQatHlGarLJAFAJB4hIASpG/QU46MGmIUVI2zfzZzi/8/ 4G/gsrS+ZYx+9Gl0CS7GiE6Nl40VpMPVOoGdFHDLdQ+WojW8NXxDDUWnkk3iQ1q5XmgF yWI2XeXvrU0vq4p1r+YZhlcqEeBQwxS3ZoTr+iRH9aD/PhAVgWQ0REpabpiYMAB4fNnp YYS/paeCl079wls+szxaoL5U0pqcTMprfepnrAgV97y2h5Ixq99VZ52mOgiqlkQE+QBL Dr1bH7OvqRbQlW7SYCRR1Jqq13BNxmNMDHnL+KbhwpxOxz4hb6PHnMCUvSmOMqmvAZCC Zvlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=logomnGm2/Va7xXc4vABdcxpFzG/aRf9J+VKYcO0+8E=; b=RrwH1wlkakWU8cVRZYekMX3+1uN1kETKDVjgBVKRj1h9eGaqnynhdJ9CveBBDC4WAU P2jyQPGL/xf4YBhGiZar879sOCJ0NF3roAetrH6ryXjluwdF3pjSJTvdkZ4ROr074k/v vqej0iEIndDr3gTLwzhZciZuF7PH3XancpTrEz3SRBITH/W1l534y5xaS6dyv4XWTAlj HERErnNoJ84sqSBtuDWF7Rqb49qF+AVs2dYXrTyatWa5oLgFF50C7DtSKK0i42WhaN0z /iFWgJbQM9IR5qolG80SwTpY2D4/EhQ0Bv2+WtxAH8ONvfnxxUzUUZfzp/ss7sPkQmbn MEvg== X-Gm-Message-State: AIkVDXIzFPklTtQwBzhGqYvBrE4MdK8ZXEXWfSoQCfjb2bN7YqXyxMVl7fcEPBy0B05HMw== X-Received: by 10.159.36.118 with SMTP id 109mr12807361uaq.124.1482174874499; Mon, 19 Dec 2016 11:14:34 -0800 (PST) From: Bart Schaefer Message-Id: <161219111435.ZM8185@torch.brasslantern.com> Date: Mon, 19 Dec 2016 11:14:35 -0800 In-Reply-To: <20161219174746.GA27982@fujitsu.shahaf.local2> Comments: In reply to Daniel Shahaf "Re: trapped in bash" (Dec 19, 5:47pm) References: <58559FC0.3080501@eastlink.ca> <161217124354.ZM7815@torch.brasslantern.com> <5855BEF2.6090208__18199.534857604$1482015164$gmane$org@eastlink.ca> <20161218150628.GB9158@fujitsu.shahaf.local2> <5856B133.9010602@eastlink.ca> <20161219003219.GA21509@fujitsu.shahaf.local2> <161218183056.ZM5304@torch.brasslantern.com> <9da2ae82-ac3f-6ee3-5452-5a008cf129e7@eastlink.ca> <161218214811.ZM5814@torch.brasslantern.com> <20161219174746.GA27982@fujitsu.shahaf.local2> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Over-reaction (was Re: trapped in bash) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Dec 19, 5:47pm, Daniel Shahaf wrote: } } Yes, error messages should generally be signed. I don't like this, for several reasons: 1. It's confusing extra information that is completely irrelevant to most users most of the time. The circumstances in which this error comes up are ridiculously rare. 2. Arguably it's not even useful extra information; anybody who would not be confused by the term "execve" already knows that's where the error must be coming from. 3. No other shell exposes this detail. That's not in itself a reason for zsh not to, but see #1 for context. 4. There are other ways (previously posted command_not_found_handler for example) to convey the equivalent information. 5. IMO Ray is deep into "if you break it, you get to keep the pieces" territory with his whole attempt to wholesale copy binaries from one architecture to another, and we should not take this as an example of situation we ought to be special-casing. 6. It's a bad precedent to distract ourselves with stuff like #5 that doesn't even rise to the level of a FREQUENTLY asked question.