On 9/25/24 12:50 PM, Robert Elz wrote:
Date: Wed, 25 Sep 2024 11:06:10 -0400
From: Chet Ramey <chet.ra...@case.edu>
Message-ID: <f0e22f19-f683-47a9-9c08-184e4a08b...@case.edu>
| So you are saying that prompt notifications and `jobs' have the same
| effect. POSIX implies but does not require this, and there is differing
| behavior among current implementatations.
What it does say in XCU 2.9.3.1 (Issue 8) is:
� If the shell is interactive and the asynchronous AND-OR list became
a background job: a message indicating completion of the corresponding
job is written to standard error. If set -b is enabled, it is unspecified
whether the process ID is removed from the list of known process IDs when
the message is written or immediately prior to when the shell writes the
next prompt for input.
which certainly implies (at the least) to me that the job needs to be
deleted by the time the next prompt is issued, either as a result of
set -b notification (if that is enabled) or by the changed status
notification that precedes each prompt (and that it is one of those
two which does it.)
It also says, before that,
"This process ID shall remain known until any one of the following occurs
(and, unless otherwise specified, may continue to remain known after it
occurs)."
Do you think the text you quoted satisfies the "unless otherwise specified?"
It's not clear.
This is why there's differing behavior.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
