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 b121b9cd for ; Mon, 29 Jul 2019 15:55:16 +0000 (UTC) Received: (qmail 3278 invoked by alias); 29 Jul 2019 15:55: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: 24101 Received: (qmail 29551 invoked by uid 1010); 29 Jul 2019 15:55:09 -0000 X-Qmail-Scanner-Diagnostics: from mail-lj1-f176.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.208.176):SA:0(-1.9/5.0):. Processed in 2.878453 secs); 29 Jul 2019 15:55: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.208.176 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=sK43EMIKMzIxkXdSnZiY3bPIGUZRLsne5W2hf/LB7ms=; b=mmJ3pvXMGCugHEN5RrAjSOtgH/eurox6kzxRTQ25vPgsIzJCr2WnKYJdIHvnWS2AOX dqWKQtgpSK6hx9/wUQrlJIQ2W+zpU44D7unq6efo1xfzzQkd1w52si9OVlEhx4jvGmF2 jT+aO6tuw2PBkbvEfO7AyufdSGq2DigXicFLWMDeOQHZPHvMBxRa1Q2lRDu0MA34JpXA iq1gViA7C4YNdAZHs2jICk6qanLXh0ds9ZegjXIomseRtD6cBFXjI48Yk4qppZySwgBn k5wmsSjnkkazZl/ZGm+cNNKYkpX+4gSFJsQV4UZ7JnCg/1MsTsXR1siWnDWp0/h9fnKM uxJA== 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=sK43EMIKMzIxkXdSnZiY3bPIGUZRLsne5W2hf/LB7ms=; b=lsKiqtwZvWvUoYsVLPbaHwatnakrrnL2aY6J4vEjf1Cb3Cw8qRczJu2xD+AH02W6Uj rEmVuCHaHz1jvqhAUd7fW03f3y21OTGPRJNnKacJK2KQP7nTKABkoJKcpmcGJKpGBJjc /nla3ljBdnBegp2MZMV3MUYDv+RBE7ylUT5UrdIPCHPD954H6Bf6nIWjiL3DoYw7T+Pr g3CCex1VElv5bCHTZQGAGb9WI+cv7QpZRnq0nCyYzt7AYWeGUr2drfsRgp2TmoflEugZ zEJKgMxOfiUhDnvq1V1pIkJzvNrWi2qXhiVN8adC9DUptxIbS2vXeqVYiA/LdqgsNB5P +vqg== X-Gm-Message-State: APjAAAUY3lHkbTGEoHihqd8gcUod6qSf7Z8uKZPMfmppZBnyPBZDDTQ+ 4dBRpFEwHt+FqR7J/PZoDBimzfgA0A9LAVRNIMdLM/kA X-Google-Smtp-Source: APXvYqw0a6aFJmP8PYlcBrlmQI1/vbiu19ndK+7oTEaA//kKz3+AzB587WkEry7oWF3VVl/aNvMv1CJJysupmzrKS2w= X-Received: by 2002:a2e:b60f:: with SMTP id r15mr57976513ljn.172.1564415671199; Mon, 29 Jul 2019 08:54:31 -0700 (PDT) MIME-Version: 1.0 References: <20190628110430.GA13790@zira.vinc17.org> <20190729152309.GA17940@cventin.lip.ens-lyon.fr> In-Reply-To: <20190729152309.GA17940@cventin.lip.ens-lyon.fr> From: Bart Schaefer Date: Mon, 29 Jul 2019 08:54:19 -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 8:24 AM Vincent Lefevre wrote: > > On 2019-06-28 13:04:30 +0200, Vincent Lefevre wrote: > > > > zira% head -n 1 <(echo foo; sleep 3; echo err >&2) > > foo > > Another issue is that if the producer side tries to access the terminal > (e.g. ssh, for a passphrase), all the processes of this side are stopped > due to a SIGTTOU signal. Even if they weren't stopped by TTOU, they'd almost certainly be stopped by TTIN. > Concerning the documentation, the zshexpn(1) man page does not say > that a process in process substitution is run in background. They have to be, otherwise either you'd need unlimited buffering or the read of the descriptor could deadlock. If you want it run in the foreground, use =(...). > Later > there's a mention of it being run asynchronously, but this term has > never been defined. In the JOBS section: If the MONITOR option is set, an interactive shell associates a job with each pipeline. It keeps a table of current jobs, printed by the jobs command, and assigns them small integer numbers. When a job is started asynchronously with `&', the shell prints a line to standard error which looks like: [1] 1234 indicating that the job which was started asynchronously was job number 1 and had one (top-level) process, whose process ID was 1234. And then in the SIGNALS section: Certain jobs are run asynchronously by the shell other than those explicitly put into the background; even in cases where the shell would usually wait for such jobs, an explicit exit command or exit due to the option ERR_EXIT will cause the shell to exit without waiting. Examples of such asynchronous jobs are process substitution, see the section PROCESS SUBSTITUTION in the zshexpn(1) manual page, and the handler processes for multios, see the section MULTIOS in the zshmisc(1) manual page.