From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25303 invoked by alias); 27 Jul 2015 18:18:01 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35940 Received: (qmail 732 invoked from network); 27 Jul 2015 18:17:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=secretsauce.net; h=cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=fpY8G UucSjNGXJzaFt5rSN+7Fqc=; b=Ymbs/Kiv7jUC6Bo55qRzdcSk50mFceNtw/+fw ngZbqlQOarHGlACp8OfaaFfpFIEZv/mxs9fKgW1S0+qEBNeXO1A0UpjH1HwLyNWx uAg68+cpyxfcq5fIzStT4TReH6Tii3KJ9PwQIgTzkBanayWIHOjxbw8vhsdGCYqh +y/V/w= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=fpY8GUucSjNGXJzaFt5rSN+7Fqc=; b=MdWx1 Q6VaTIHn0fJOzto+74Qj683BBCb9MmNQWNe6/Z34kGWiO9Vvsf7DZ2HtRgeiEyaZ xbmD0+0lL4a9i1DBm+4D/Ge+RvGp1Mwa7bQBYPdbiv1swYVB8BOHOZ3zskHk4pR/ tFjEcmlezfHhkJbXiBwCSTCB154h/wX7yKYFY0= X-Sasl-enc: POdiCugWNwCP1rs150Xph8Nsb+MT4zFopWLYY/uNBBMK 1438021076 References: <87lhe23psr.fsf@secretsauce.net> <150727091512.ZM6365@torch.brasslantern.com> <150727093727.ZM6467@torch.brasslantern.com> From: Dima Kogan To: Bart Schaefer Cc: zsh-workers@zsh.org Subject: Re: zargs parallelization support blows up with |& In-reply-to: <150727093727.ZM6467@torch.brasslantern.com> Date: Mon, 27 Jul 2015 11:19:45 -0700 Message-ID: <87k2tl4g5a.fsf@secretsauce.net> MIME-Version: 1.0 Content-Type: text/plain Bart Schaefer writes: > On Jul 27, 9:15am, Bart Schaefer wrote: > } > } The problem is that when you append a pipe to the end, zargs ends up > } as a subshell, and you can't do job control in a subshell (which you > } would have seen if you weren't grepping stderr): > } > } (eval):wait:1: can't manipulate jobs in subshell > > This turned out to be easier to fix than I expected: > > The patch works well for me. Thanks!