From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33264-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 14118 invoked by alias); 28 Sep 2014 18:04:49 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 33264
Received: (qmail 8207 invoked from network); 28 Sep 2014 18:04:46 -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
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <140928110438.ZM27132@torch.brasslantern.com>
Date: Sun, 28 Sep 2014 11:04:38 -0700
In-reply-to: <140927165554.ZM32155@torch.brasslantern.com>
Comments: In reply to Bart Schaefer <schaefer@brasslantern.com>
 "Re: SIGPIPE (Re: ZSH history not saved anymore)" (Sep 27,  4:55pm)
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>
	<CABx2=D9xdeJ0qDNayUG0astemFEtK13SLpA3j8UQT5EqHW_PmA@mail.gmail.com>
	<87y4t66td0.fsf@thinkpad-t440p.tsdh.org>
	<CABx2=D-chwqBDZLTk8OqeUDqxvnYUQFFKWbiw7h3ZgUGtSb_CQ@mail.gmail.com>
	<871tqxqyil.fsf@thinkpad-t440p.tsdh.org>
	<140927105301.ZM31550@torch.brasslantern.com>
	<20140927214035.7af22023@pws-pc.ntlworld.com>
	<140927165554.ZM32155@torch.brasslantern.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: SIGPIPE (Re: ZSH history not saved anymore)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Sep 27,  4:55pm, Bart Schaefer wrote:
}
} Usually a SIGPIPE is generated by a write on a descriptor whose "other
} end" is closed.  So I'm wondering if there are cases where a subshell
} might get a SIGPIPE on write, in which not only should it not zexit()
} but it shouldn't exit at all?

Behavior before patch:

torch% (sleep 5; echo hello; print -u2 continued after PIPE) | (exit)
torch% 

Behavior after patch in 33257:

torch% (sleep 5; echo hello; print -u2 continued after PIPE) | (exit)
echo: write error: broken pipe
zsh: write error: broken pipe
continued after PIPE
torch% 

No history saved in either case, so at least that part is OK, but the
patch obviously breaks something in subshells.