From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28444 invoked by alias); 15 Nov 2010 17:25:18 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 15548 Received: (qmail 15204 invoked from network); 15 Nov 2010 17:25:07 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <101115092438.ZM29576@torch.brasslantern.com> Date: Mon, 15 Nov 2010 09:24:38 -0800 In-reply-to: <20101115163234.GE19451@prunille.vinc17.org> Comments: In reply to Vincent Lefevre "Re: strange behavior" (Nov 15, 5:32pm) References: <20101102120943.GK19295@prunille.vinc17.org> <20101115163234.GE19451@prunille.vinc17.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: strange behavior MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Nov 15, 5:32pm, Vincent Lefevre wrote: } } > ypig:~/wd> up } > At revision 40202. } > zsh: exit 141 } > ypig:~/wd[PIPE]> } } This has just happened again. This time, the machine hadn't been } rebooted (but there has been a lot of disk activity before that). It appears to me that it must be the case that svn "$@" is exiting with status 141, rather than that the filter function is killing its parent with a PIPE signal. That in turn must be happening "inside" svn somewhere.