On 11/8/23 8:12 PM, Steffen Nurpmeso wrote:
The "problem" with the current way bash is doing it is that bash's
job handling does not recognize jobs die under the hood:
$ jobs
[1]- Stopped LESS= less -RIFe README
[2]+ Stopped LESS= less -RIFe TODO
$ kill $(jobs -p)
$
^ nothing
$ jobs
[1]- Stopped LESS= less -RIFe README
[2]+ Stopped LESS= less -RIFe TODO
Yes, the jobs are still stopped, and will remain stopped until they get
a SIGCONT. Do you think that kill, when given a pid argument, should look
up any job associated with that pid and send it a SIGCONT? Or should it
send a SIGCONT to the pid unconditionally? If so, what about other
processes in that job?
--
``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/
