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

[Jonathan Kamens]

Chet Ramey writes:
 > > 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.

OK, on the one hand, I see what you're saying, but on the other hand,
why not leave functionality in place that worked for years, was
probably gotten used to by thousands if not tens of thousands of
people, and doesn't hurt anything?

  jik