Hi Chet,
I wrote:
> > 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?
BTW, you are aware that shells like csh do this, so bash may not have
been doing it by accident, even if the implementation suggests that?
Cheers,
--
Ralph Corderoy. http://inputplus.co.uk/ralph/http://troff.org/