We have some UNIX conformance test suites which are failing,
specifically
they're failing on the %% job argument essentially as follows:
#!/bin/bash
cat &
kill -1 %% && echo I killed it || echo could not kill it
If you run this script, it will emit an error saying the %% argument
to kill
is invalid and it could not kill the job. Looking into
builtins/kill.def,
you see that it specifically checks interactive and job_control (both
of which
are 0 in the case of a shell script) and disables the code which
would expand
the %% form in the script. Are you sure this is correct? The Open
Group,
which uses this in a number of its job control test scripts, doesn't
appear to think so... Thanks!
OK, we'll try it. The next version of bash will not require job
control to be enabled when using job id notation as arguments to
`jobs', `kill', and `wait'.
The necessary plumbing is all there; we'll see how it goes.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU chet@po.cwru.edu
http://tiswww.tis.cwru.edu/~chet/