Thorsten Glaser <[email protected]> wrote: |Steffen Daode Nurpmeso dixit: |> |A brute force thing could be to patch the shell to run j_sigchld() |> |every time the job control builtins and kill are run (this will |> |still miss some, like async notify when /bin/kill is used instead). |> |>I think this is what the other shells (bash(1) and ksh(1) that is) |>necessarily do, but i'd agree it's a flaky approach of doing |>things and as such not worth the effort. (I.e. far less than | |Hm. I slept over it, and doing a waitpid run in two more places, |– right before the jobs and maybe wait builtins, and |– just after a command was run, before calling edit.c, |sounds doable. | |Ideas? Or is this crazy?
I think i've misread what you said and also misunderstand; i haven't looked at the other shells, but i think what they (necessarily) do due to lack of a true WIFCONTINUED() is that they track a «logical» state-change, as in (1) you STOP it, it's stopped, (2) you CONTinue it, it's running again. In doing so they nicely workaround a non-functioning WIFCONT but of course miss updates that may happen via whatever kill that is not builtin to the managing shell. I indeed thought that mksh(1) doesn't do the manual tracking because it doesn't work if bypassed like that, and i do think that is the better thing to do, because it is *true*; maybe it could be documented so that a «normal» user gets it right (as it's not worse than e.g. bash(1), only true), however. I'm afraid you're not willing to accept a documentation patch from my side… |bye, |//mirabilos --steffen
--- Begin Message ---Steffen Daode Nurpmeso dixit: > |A brute force thing could be to patch the shell to run j_sigchld() > |every time the job control builtins and kill are run (this will > |still miss some, like async notify when /bin/kill is used instead). > >I think this is what the other shells (bash(1) and ksh(1) that is) >necessarily do, but i'd agree it's a flaky approach of doing >things and as such not worth the effort. (I.e. far less than Hm. I slept over it, and doing a waitpid run in two more places, – right before the jobs and maybe wait builtins, and – just after a command was run, before calling edit.c, sounds doable. Ideas? Or is this crazy? bye, //mirabilos -- 20:49⎜«Natureshadow» Oops, jetzt hab ich mir doch glatt beim Trinken ⎜ Mineralwasser ins Ohr gekippt… 21:04⎜«mirabilos» ist das siggbar? █ PS: سمَـَّوُوُحخ ̷̴خ ̷̴خ ̷̴خ امارتيخ ̷̴خ 21:05⎜«Natureshadow» mirabilos: was sollte dich davon abhalten…
--- End Message ---
