Seb dixit:
>Ok. In fact mksh works like dash in this case... but even with the
>"set -m" option mksh still ignores it, by there.
Without looking at the code, this might be true. Jobs have
really only be used in interactive shells.
>BTW, I recently submitted on the dash ML the idea that kill could
>reach "%" jobs independently from the state of the job control flag.
If you really need that, you’re welcome to submit a patch ☺
>As a matter of fact, if it's not a requirement, POSIX seems to
>encourage it:
>
> The jobs utility is not dependent on the job control option, as are
> the seemingly related bg and fg utilities because jobs is useful for
Right. The jobs, fg, bg commands *are* available in scripts and
other places where full job control isn’t enabled, unless job
control is not compiled in due to OS bugginess.
[ signal numbers ]
>Not all of them, indeed... but as far as it makes sense I try to
>stick with POSIX shell for scripting. :)
Note that, at least for the trap builtin, signal numbers are
not accepted by POSIX, only signal names. (I’m not in the mood
to check it for kill right now as I have a headache.)
trap 'exit 1' 1 2 3 13 15 # not POSIX!
bye,
//mirabilos
--
13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good
guy. But he's always right! In every fsckin' situation, he's right. Even
with his deeply perverted taste in software and borked ambition towards
broken OSes - in the end, he's damn right about it :(! […] works in mksh
