Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: 'wait' exit status and warnings [was: The big kre zsh bug report]
- X-seq: zsh-workers 43958
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: 'wait' exit status and warnings [was: The big kre zsh bug report]
- Date: Sun, 30 Dec 2018 18:13:18 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1546193598; bh=cpyJZk7kyoju5civ/7AxcGceA4SK21VVcpZIlqQubl4=; h=Subject:From:To:Date:In-Reply-To:References; b=t5WiTf5AY1lTahZ5kA9TNKxYbxgfxSrLGorPno9cn+3Z5+nMcfPDyWAAcmOTKEAXG nYHXT6ungnTePTE+IVMiqXzP6XjYbBjZ2sk3CGd5WnQKVET335JY1ZvulxPPZLh2ON AaEmIslipkvsqd2M5x97+7Vf1fOTuJMrCD7ATQbWDLDPJ0Mel/rKylpjzG+HZ9ep0w rjXPQfg/0rMtxFOP6dEEQZOWbrJGr46l4abirr/RjPazBsrCi0TebzKyFB+2jtJv9I jfFOatygPDTa2HAN57IZi09wAC/+q1ypRGRtFR2vJj4a3zfmntABL67dcLQP2Bl1cN u13BcDEKic2Kw==
- In-reply-to: <bb6689f2-5d9a-da96-46b8-69d34f08fdf2@inlv.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <d7b0451f90bdfe61f48cc1361690180e07158900.camel@ntlworld.com> <b8851c3a50bd8bceba1961f2f764e1a6869481ac.camel@ntlworld.com> <18f684a8-2fec-4ebe-a63e-cf6688ae519f@inlv.org> <CAH+w=7bthv3E3Lr3UC9FvroXFcS1W+fDRuS6CLPxy_eyX0szqw@mail.gmail.com> <bb6689f2-5d9a-da96-46b8-69d34f08fdf2@inlv.org>
On Tue, 2018-12-25 at 20:44 +0000, Martijn Dekker wrote:
> Op 21-12-18 om 07:53 schreef Bart Schaefer:
> > On Thu, Dec 20, 2018 at 2:48 PM Martijn Dekker <martijn@xxxxxxxx> wrote:
> > > > tc-so:Executing command [ zsh --emulate sh -c wait 1 ]
> > > > tc-se:Fail: incorrect exit status: 1, expected: 127
> >
> > Probably easily fixed.
>
> Well, kind of.
>
> I got as far as the attached patch, but it turns out there is another
> bug with 'wait': '(wait %1)' in a subshell quietly returns status 0 even
> if there is no such job. ('(wait %2)' and up are ok.)
Thanks --- for now I've committed this with the test doctored and a note
in the test file.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author