From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 57969dc4 for ; Sat, 6 Jul 2019 23:56:18 +0000 (UTC) Received: (qmail 27057 invoked by alias); 6 Jul 2019 23:56:11 -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: List-Unsubscribe: X-Seq: 24025 Received: (qmail 29404 invoked by uid 1010); 6 Jul 2019 23:56:11 -0000 X-Qmail-Scanner-Diagnostics: from joooj.vinc17.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25496. spamassassin: 3.4.2. Clear:RC:0(155.133.131.76):SA:0(-1.9/5.0):. Processed in 0.75714 secs); 06 Jul 2019 23:56:11 -0000 X-Envelope-From: vincent@vinc17.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at vinc17.net does not designate permitted sender hosts) Date: Sun, 7 Jul 2019 01:55:37 +0200 From: Vincent Lefevre To: zsh-users@zsh.org Subject: Re: kill the LHS command of a pipe once the RHS command terminates Message-ID: <20190706235537.GB14626@zira.vinc17.org> Mail-Followup-To: zsh-users@zsh.org References: <20190628110430.GA13790@zira.vinc17.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Mailer-Info: https://www.vinc17.net/mutt/ User-Agent: Mutt/1.12.1+33 (6a74e24e) vl-117499 (2019-06-23) On 2019-06-29 09:17:13 -0700, Bart Schaefer wrote: > zsh% coproc { echo foo; sleep 3; echo err >&2 }; head -n 1 <&p; kill %+ > [1] 53747 > foo > zsh% > [1] + terminated { echo foo; sleep 3; echo err >&2; } > zsh% > > If you're going to kill the right-side with an interrupt or other > signal, you'll have to arrange to trap that so that the subsequent > kill isn't also skipped. Also in practice you want something more > specific than "kill %+" which could kill the wrong job if you have > multiple backgrounded jobs and the coproc exits before the kill > occurs. Something like that seems to work: unsetopt NOTIFY coproc ... local j="${${$(jobs %+)%%]*}#\[}" less -f <&p kill %$j but I would like to get rid of the job status that appear at the end. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)