On Tuesday, August 6, 2024, Zachary Santer <zsan...@gmail.com> wrote: > > How bash is actually used should guide its development.
Correct. No one waits for procsubs in their scripts or on the command line. In a script, a child process being a job or not makes no difference, > from the shell programmer's perspective, unless you've got job control > on for some reason. That's not true. `jobs' works even if job control is disabled. `kill' accepts jobspecs and bash expands the `\j' escape sequence in prompt strings. So it does make a difference. > Only as much noise as how many procsubs you expand on the command line. > And that's too many. Much more than async jobs. -- Oğuz
