> How come "%" by itself no longer works to bring the most recent job to
> the foreground in bash 3.0? This seems like a regression in
> functionality. Is it intentional?
Yes, it was intentional. The null job was never valid, and only worked by
an accident of implementation. I tightened the code up, and this was a
result.
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/