From: Eric Nielsen <firstname.lastname@example.org>
To: Bart Schaefer <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: zargs with -P intermittently failing in zsh 5.9 and macOS
Date: Tue, 24 May 2022 15:21:47 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
On May 24, 2022, Bart Schaefer <email@example.com> wrote:
> zargs was re-coded as of the 5.9 release so that it waits for
> individual jobs instead of using a single "wait" for all of them.
> This means it can detect nonzero exit in cases where earlier revisions
> missed it.
Got it. So we're now seeing a more precise return code than before 5.9.
> Something is causing the subshell that was running f to exit with
> status 19 even though f returned 0.
Any idea what could be returning 19? Looks like it's something outside
the scope of f. At least the code is consistently 19, when it happens.
[-- Attachment #2: Type: text/html, Size: 3160 bytes --]
next prev parent reply other threads:[~2022-05-24 20:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 16:09 Eric Nielsen
2022-05-24 17:32 ` Bart Schaefer
2022-05-24 20:21 ` Eric Nielsen [this message]
2022-05-24 20:35 ` Bart Schaefer
2022-05-26 8:57 ` Jun T
2022-05-26 11:21 ` Jun. T
2022-05-27 3:39 ` Bart Schaefer
2022-05-27 4:18 ` Lawrence Velázquez
2022-05-27 5:29 ` Jun T
2022-05-27 16:10 ` Bart Schaefer
2022-05-27 17:25 ` Jun. T
2022-05-29 3:30 ` Bart Schaefer
2022-05-29 14:47 ` Jun. T
2022-05-29 20:07 ` Bart Schaefer
2022-05-30 11:16 ` Jun T
2022-06-07 6:51 ` Jun T
2022-06-09 2:56 ` Bart Schaefer
2022-06-12 16:43 ` Eric Nielsen
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).