Re: When/why does the shell (bash) (sometimes) not re-cycle job IDs?

In article <v1qr6l$2qsv6$1@dont-email.me>,
Janis Papanagnou  <janis_papanagnou+ng@hotmail.com> wrote:
...

Job numbers are reused after it has notified you of termination of the
previous job. At least in Bash.

>
Also the same behavior in Ksh, ever since I can remember; lowest job
number "available" gets re-used first. (Where "available" means that
its finishing status has been reported and not that the job finished.)

 
Nope.  Sorry.

>
I read that as "in Bash it's not the case". - Can't tell; I can just
say that what LDO was claiming for Bash at least is the behavior for
Ksh. (You are not arguing that Ksh would behave differently, do you?)

You said that it does the right thing in ksh (*).  LDO claimed
(incorrectly) that it does the right thing in bash.  You then claimed that
it does the same thing in ksh as in bash, which is, clearly, incorrect.
Hence my Nope, Sorry.

(*) I have, just now, verified that it does the right thing in ksh - that
is, whatever version of ksh was laying around on this system for me to test
with.

P.S.  I have also verified that, as noted by Christian, it does the wrong
thing in tcsh as well.  I have not (yet) verified his statement about
things changing (in tcsh) when you have more than 9 background jobs...


--
On the subject of racism being depicted in the media, the far right and the far left have
met up in agreement (sort of like how plus infinity meets up with minus infinity).
The far left doesn't want it, because they are afraid it will make people racist.
The far right doesn't want it, because they are afraid it will make people feel bad about being racist.