On 5/2/24 1:38 PM, Oğuz wrote:
On Thursday, May 2, 2024, Chet Ramey <chet.ra...@case.edu
<mailto:chet.ra...@case.edu>> wrote:
It doesn't. In an interactive shell, while executing a command list,
every shell prints a notification if a foreground job is killed by a
signal before executing the next comamnd in the list. Nobody waits
until issuing the next prompt. The standard doesn't cover that, maybe
intentionally.
Only zsh and bosh decorate the notification like `jobs' does; others
including Sun and SCO ksh88 print only a string describing the signal.
Oh, shells are all over the map here.
I think we're talking about two different categories of notifications though; the one sent when a foreground job is killed is useful when the shell is non-interactive too, the other not so much. I don't know why the standard doesn't cover it, but if you plan to follow zsh in this I don't think that's a good idea. It's ugly and confusing.
I'm not planning to change the text. The point is whether or not this
counts as `notification' for the purposes of the jobs list, which allows
the shell to remove the job from the list.
--
``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
