Re: "%" no longer works in bash 3.0?

[Ralph Corderoy]

Hi Chet,

> > 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.

That's a shame for those of us that have been using just % for so long
we've forgotton just how long that is.  Any chance it can be put back
again without it being an accident of implementation?

Cheers,

-- 
Ralph Corderoy.      http://inputplus.co.uk/ralph/     http://troff.org/