On 4/27/24 5:15 PM, Koichi Murase wrote:
I'm currently testing my framework with 5.3-alpha. In 5.3-alpha and the devel branch, foreground dead jobs are reported by the `jobs' builtin with function substitutions:
OK, let's explore this again. POSIX says `jobs' should report on
"the status of all background jobs, both running and suspended, and all
jobs whose status has changed and have not been reported by the shell."
So the question is what exactly constitutes a foreground job whose status
has "not been reported." Does that exempt terminated foreground jobs whose
status would not be reported when the shell reaps jobs before printing
$PS1? That would be jobs that exited normally or jobs that exited due to
a signal we don't report on (SIGINT, possibly SIGPIPE, in interactive
shells). Or is it jobs that have changed status and the shell hasn't yet
determined whether it will notify the user about them?
--
``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/
OpenPGP_signature.asc
Description: OpenPGP digital signature
