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 21:58:27 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 6
Message-ID: <vn6b63$50b2$11@dont-email.me>
References: <vn2v1c$2s2ce$1@dont-email.me> <vn3u8a$35e2n$8@dont-email.me>
	<vn3vdk$3686j$1@dont-email.me> <vn45ut$37klv$6@dont-email.me>
	<vn58ti$3o8mi$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 22:58:27 +0100 (CET)
Injection-Info: dont-email.me; posting-host="242dfd8966dadc131984b5b1dada7143";
	logging-data="164194"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/kpajMDlZaXyNelgXkofwT"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:vj2yuGDnVCyPNfROK8HY2/BIEwk=
Bytes: 1349

On Sun, 26 Jan 2025 13:13:37 +0100, Janis Papanagnou wrote:

> You initiate jobs, say, by something like 'a_command &', the command
> gets registered in a shell table. And at any time you can 'wait' for it.

The “wait” command doesn’t require you to specify which job to wait for.