From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21894 invoked by alias); 27 Sep 2014 20:40:58 -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: 33258 Received: (qmail 28949 invoked from network); 27 Sep 2014 20:40:45 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-Originating-IP: [80.3.229.105] X-Spam: 0 X-Authority: v=2.1 cv=Cq4xcxID c=1 sm=1 tr=0 a=uz1KDxDNIq33yePw376BBA==:117 a=uz1KDxDNIq33yePw376BBA==:17 a=NLZqzBF-AAAA:8 a=uObrxnre4hsA:10 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=WR_zTrULppFQ69D25doA:9 a=CjuIK1q_8ugA:10 a=I6wTmPyJxzYA:10 Date: Sat, 27 Sep 2014 21:40:35 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: SIGPIPE (Re: ZSH history not saved anymore) Message-ID: <20140927214035.7af22023@pws-pc.ntlworld.com> In-Reply-To: <140927105301.ZM31550@torch.brasslantern.com> References: <87mw9qdp7s.fsf@thinkpad-t440p.tsdh.org> <20140924200710.2f764272@pws-pc.ntlworld.com> <8738bg2n1v.fsf@thinkpad-t440p.tsdh.org> <140926000448.ZM30835@torch.brasslantern.com> <878ul6lrw9.fsf@thinkpad-t440p.tsdh.org> <87y4t66td0.fsf@thinkpad-t440p.tsdh.org> <871tqxqyil.fsf@thinkpad-t440p.tsdh.org> <140927105301.ZM31550@torch.brasslantern.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sat, 27 Sep 2014 10:53:01 -0700 Bart Schaefer wrote: > I'm a bit hesitant to change this after all these years, but perhaps an > interactive shell should exit on SIGPIPE if the terminal is not still open? It's hard to see how can that be wrong if we exit on EOF on the terminal. > I'm probably missing something having to do with subshells receiving the > PIPE signal. There are regrettably many code paths covering all the ways > an interactive shell might fork. I don't know what it is that stops it running zexit() and having the same effect in a subshell, hence writing out history incorrectly, if that's what you mean, but you may be thinking of something more subtle. pws