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

In article <slrnv3vt5j.1gfp.naddy@lorvorc.mips.inka.de>,
Christian Weisgerber  <naddy@mips.inka.de> wrote:

On 2024-05-11, Kenny McCormack <gazelle@shell.xmission.com> wrote:
>

I tried it a few times, but could not get back the #1 slot.

>
If no job is running, a new job gets 1, otherwise new jobs are
numbered consecutively.

Yeah, that seems to be it.  I wonder why...

...

As I accidentally discovered while looking at the code, csh(1) tries
to recycle smaller job IDs once it goes beyond 9.  tcsh(1) preserves
that behavior to this day.

That's weird.  I wonder why...

I offer no opinion on this, nor on the Plan 9 assertion that job
control is a poor hack and you should just open another window.

Well, certainly, having lots of windows open (and having things like
screen/tmux) is nice and is the modern way, but this is one situation where
I actually like having these other things running as jobs.  If they were in
other windows (and/or in screen/tmux windows), I'd lose track of them.

As it is, I sometimes forget they are there.

--
Politics is show business for ugly people.

Sports is politics for stupid people.