From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16474 invoked from network); 15 Jun 2005 13:57:05 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 15 Jun 2005 13:57:05 -0000 Received: (qmail 85169 invoked from network); 15 Jun 2005 13:56:59 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 15 Jun 2005 13:56:59 -0000 Received: (qmail 12766 invoked by alias); 15 Jun 2005 13:56:57 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 21344 Received: (qmail 12756 invoked from network); 15 Jun 2005 13:56:56 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 15 Jun 2005 13:56:56 -0000 Received: (qmail 84874 invoked from network); 15 Jun 2005 13:56:56 -0000 Received: from mailhost1.csr.com (HELO MAILSWEEPER01.csr.com) (81.105.217.43) by a.mx.sunsite.dk with SMTP; 15 Jun 2005 13:56:51 -0000 Received: from exchange03.csr.com (unverified [10.100.137.60]) by MAILSWEEPER01.csr.com (Content Technologies SMTPRS 4.3.12) with ESMTP id for ; Wed, 15 Jun 2005 14:54:56 +0100 Received: from news01.csr.com ([10.103.143.38]) by exchange03.csr.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 15 Jun 2005 14:57:22 +0100 Received: from news01.csr.com (localhost.localdomain [127.0.0.1]) by news01.csr.com (8.13.1/8.12.11) with ESMTP id j5FDunhh015705 for ; Wed, 15 Jun 2005 14:56:49 +0100 Received: from csr.com (pws@localhost) by news01.csr.com (8.13.1/8.13.1/Submit) with ESMTP id j5FDunra015702 for ; Wed, 15 Jun 2005 14:56:49 +0100 Message-Id: <200506151356.j5FDunra015702@news01.csr.com> X-Authentication-Warning: news01.csr.com: pws owned process doing -bs To: zsh-workers@sunsite.dk Subject: Re: subtle `echo' bug In-reply-to: <200506150910.j5F9AEFa009630@news01.csr.com> References: <20050614172738.GL4685@solemn.turbinal.org> <200506142212.24133.arvidjaar@newmail.ru> <1050615002844.ZM7767@candle.brasslantern.com> <200506150910.j5F9AEFa009630@news01.csr.com> Date: Wed, 15 Jun 2005 14:56:48 +0100 From: Peter Stephenson X-OriginalArrivalTime: 15 Jun 2005 13:57:22.0940 (UTC) FILETIME=[276B7BC0:01C571B2] X-Spam-Checker-Version: SpamAssassin 3.0.2 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=6.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.2 X-Spam-Hits: -2.6 Peter Stephenson wrote: > You can show this up with > > trap '' PIPE > > which causes zsh to report the error as a side effect (for reasons I > haven't investigated: possibly the error message isn't getting time to > emerge in the other case, which may be a bug). This is rather garbled: the error message shown was a write error which you certainly wouldn't see if the process that failed to write received a SIGPIPE. The question is whether the rest of the shell should indicate the failure. I think some shells indicate when a child received SIGPIPE. Experimentation suggests a SIGPIPE to a subprocess in a pipeline in other shells doesn't cause the shell to abort execution. I'm not sure where the logic in zsh is that's causing this. -- Peter Stephenson Software Engineer CSR PLC, Churchill House, Cambridge Business Park, Cowley Road Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. **********************************************************************