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=DKIM_SIGNED,DKIM_VALID, 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 529854e3 for ; Mon, 29 Jul 2019 23:43:15 +0000 (UTC) Received: (qmail 18733 invoked by alias); 29 Jul 2019 23:43:09 -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: 24109 Received: (qmail 8429 invoked by uid 1010); 29 Jul 2019 23:43:09 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf1-f45.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.2/25524. spamassassin: 3.4.2. Clear:RC:0(209.85.167.45):SA:0(-1.9/5.0):. Processed in 2.823467 secs); 29 Jul 2019 23:43:09 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.167.45 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=N+Xlz0LFYklknVsHq1VLxZH3N+6NGpH21d1cpLsQUh0=; b=e5JvLM3q+5ZC6R24VY3SSF8D8LC/reIRioyxB7VDuBqgkNXK2r56j0RE9XormLN1WB dbge5vtILbXc4hziBI6u5nzKcczXhJYY8wPFKtHoYfr1apFBi7ZsOOu8TgD1QGrMCdnO 9/sN7NZtgoMQ/jVlDnULobc2vNXQEbMIBxYHnNBjHyxrsObu8Npq7MFjErAFq0osmWkj kqbzhyHK8riWCueyfbkqBrAITYGUc0MYDzS9Asz5x2MmyYRgdZUeKeqv7FLvYyz0EtaC 7zDXR8vlNBjhNMm9Q36/JcEZDiQ2nOy5ml7dD3Oo2r8/4ycuxwBUHezn1eNlwJPNhp7k wfCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=N+Xlz0LFYklknVsHq1VLxZH3N+6NGpH21d1cpLsQUh0=; b=IZtdwgBe1BbFhbSUVAC5LLmRJVJqjpWn9gCpbjA1P6sv7K03QF3FI/ftat6HEFAznR gBnAtfgCiUMdABBT1QnBSm8ujowvLa/bfLfi2A5ZUuN0zWi1gBPZVjffqIPzRKPXwMlV zt6sEu9Ny8XN4QcLTjdAfXvhGy54lhWmyFbgkpBSNsbpn8auANOsiBnAo/hBr5BL5zOA Y1rSNtENMpdW6EsKgpjVptNYzmW7u/hz5ry5bK5veAcncOAnRkyK9l7ec783NPg1Wt8d dwqDPD9Vkleq8v8HpQUZBfHx+dhxEb316PrK6R7DL2CHCdcJH0ihAnlpnSk4XadBlfJ2 FspQ== X-Gm-Message-State: APjAAAXqV89yKfxA6Zav6i6MwNt6KQrV0x5B/y3uev9pJCnraM0PGYRB hjXUiVU4tj6cYiuqwYGQhA7TTLw3/H6+iiquVhN0AA== X-Google-Smtp-Source: APXvYqyRhDLIs6dgZ4Q0XrylBIixJufAtcLZPnqkRC/WNyOhc4woHSFyh/AksJeS20eStfmTwlZUC2Qh7uAsmV5uK8k= X-Received: by 2002:ac2:42c7:: with SMTP id n7mr52418151lfl.65.1564443750384; Mon, 29 Jul 2019 16:42:30 -0700 (PDT) MIME-Version: 1.0 References: <20190628110430.GA13790__36317.6205357135$1561719956$gmane$org@zira.vinc17.org> <20190628184134.btrejxp7jyoo6wz6@chaz.gmail.com> <20190629012433.GA23526@zira.vinc17.org> <20190629153055.kb444goqcmpfblac@chaz.gmail.com> <20190706234919.GA14626@zira.vinc17.org> <20190729230817.GA13849@zira.vinc17.org> <20190729231503.GB28524@zira.vinc17.org> In-Reply-To: <20190729231503.GB28524@zira.vinc17.org> From: Bart Schaefer Date: Mon, 29 Jul 2019 16:42:18 -0700 Message-ID: Subject: Re: kill the LHS command of a pipe once the RHS command terminates To: Zsh Users Content-Type: text/plain; charset="UTF-8" On Mon, Jul 29, 2019 at 4:15 PM Vincent Lefevre wrote: > > zira% (trap '' INT; svn log | { (trap - INT; less;); kill -PIPE 0; }) This is fine, but note that "kill ... 0" sends the signal to the whole process group, which might have unexpected side-effects. Bash and ksh93 manage process groups differently than zsh; this is related to the way zsh runs the right-hand-side of pipelines in the current shell when it can. I don't know about dash or mksh, but but they must have more zsh-like group management.