Buggy job control

Question

Buggy job control

mgree opened this issue 6 years ago · 3 comments

There are some bugs in interactive job control.

ab3aa4d#diff-597a09bc85e5022f70eb206c759b4b85 was accidentlly using job control in pipes, breaking, e.g., hostname | wc -l
need to be careful update current job statuses on ECHLD
Sh_notify should trigger ASAP on SIGCHLD

Answer 1 · 2019-06-12T13:29:47.000Z

Break from loops, etc., when a command exits due to SIGINT (status 130) (cf. dash)
INTON/INTOFF à la dash to get correct command editing behavior

If sh receives a SIGINT signal in command mode (whether generated
by typing the interrupt character or by other means), it shall
terminate command line editing on the current command line,
reissue the prompt on the next line of the terminal, and reset the
command history (see fc) so that the most recently executed
command is the previous command (that is, the command that was
being edited when it was interrupted is not re-entered into the
history).

Answer 2 · 2019-06-13T01:11:39.000Z

echo hi | sleep 3, ^Z, fg doesn't work. Some bugs fixed in 7a75e15 (wasn't properly simulating killpg), but we're not all the way there yet.

Answer 3 · 2019-06-13T18:46:31.000Z

smoosh -c 'echo | smoosh -i' is blocking on taking the foreground. everything else seems to be okay in 3fc4dd4