Re: (bash) How (really!) does the "current job" get determined?

On 04.10.2024 19:49, Christian Weisgerber wrote:

On 2024-10-04, Kaz Kylheku <643-408-1753@kylheku.com> wrote:
 

What? Scripting should not go anywhere near POSIX job control, which is
an interactive feature that requires a terminal session.

 
Well, there _is_ set -m.

And how will that devaluate what Kaz has said? Please elaborate.

See also Bolsky/Korn (chapter "Job Control") about some details
on implicit and explicit activation, implementation dependencies,
and use of option 'monitor' (-m) [for interactive invocations]
for systems that don't support ("complete") job control.

If you have other information (facts, rationales, or insights),
or if you know of any useful and sensible application contexts
for non-interactive usages I'd certainly be curious to know.[*]

Janis

[*] The job-control "layering" that Kaz mentioned was the only
thing that appeared somewhat obvious to me. I also don't expect
any insights from the OP (who obviously was in insult-mode), so
feel free to jump in.