Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.unix.shell
Subject: Re: ksh - issue with (non-existing) jobs
Date: Sun, 26 Jan 2025 02:17:01 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <vn45ut$37klv$6@dont-email.me>
References: <vn2v1c$2s2ce$1@dont-email.me> <vn3u8a$35e2n$8@dont-email.me>
	<vn3vdk$3686j$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 26 Jan 2025 03:17:01 +0100 (CET)
Injection-Info: dont-email.me; posting-host="242dfd8966dadc131984b5b1dada7143";
	logging-data="3396287"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18r6NKs4bkdmMjV8y5CQyf/"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:R6atVT3UCaBOCtW5sNgF78IExmo=
Bytes: 1377

On Sun, 26 Jan 2025 01:25:22 +0100, Janis Papanagnou wrote:

> I'd guess, though, that it wouldn't have helped ...

Well, if you explicitly waited for a job it couldn’t find, then you would 
be right. But given it is capable of waiting in general for any job to 
terminate, it might take a different path through the code that is not 
afflicted by the same state confusion.