From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18594 invoked by alias); 22 Oct 2014 15:48:24 -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: 33508 Received: (qmail 27721 invoked from network); 22 Oct 2014 15:48:22 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) 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.2 From: Bart Schaefer Message-id: <141022084821.ZM17298@torch.brasslantern.com> Date: Wed, 22 Oct 2014 08:48:21 -0700 In-reply-to: Comments: In reply to Tim Speetjens "Re: bug in zsh wait builtin - rhbz#1150541" (Oct 22, 10:42am) References: <20141021210234.199eee3d@pws-pc.ntlworld.com> <141021235542.ZM14840@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org, zsh-workers@zsh.org Subject: Re: bug in zsh wait builtin - rhbz#1150541 Cc: Tim Speetjens MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Oct 22, 10:42am, Tim Speetjens wrote: } } Are there any plans, to make zsh behave more like other shells, with } regard to this? Both bash and mksh do what one would expect: propagate } the return code, even if the job finished meanwhile. I would say there are "intentions" rather than "plans". There must be something there already for { setopt POSIX_JOBS; foo & wait $! } so it may be possible to generalize. I'm still curious about PID rollover and whether "kill $!" is supposed to avoid signalling the wrong job.