Thank you for a quick fix. Bash 5.2.21 with the patch applied no longer
exhibits the problem in my tests.
-Mark
On Thursday, June 27, 2024 at 06:05:28 AM PDT, Chet Ramey
wrote:
On 6/18/24 4:55 PM, Mark March wrote:
> I am working with a large Bash code base where most scripts disable
On 6/18/24 4:55 PM, Mark March wrote:
I am working with a large Bash code base where most scripts disable job control
and the DEBUG trap is used extensively. I noticed that if I tried to run my
scripts in the background, the interactive shell that started them would
immediately exit on any key
On 6/25/24 2:49 PM, Mark March wrote:
Bump in case this fell through the cracks. My simple script that uses no job
control facilities (in fact, turns job control off) if run in the background
would log the user out on any keyboard input. This can't be right. Can you at
least confirm that thi
Bump in case this fell through the cracks. My simple script that uses no job
control facilities (in fact, turns job control off) if run in the background
would log the user out on any keyboard input. This can't be right. Can you at
least confirm that this is indeed a bug in Bash? Are there any
I am working with a large Bash code base where most scripts disable job control
and the DEBUG trap is used extensively. I noticed that if I tried to run my
scripts in the background, the interactive shell that started them would
immediately exit on any keyboard input. A simple repro is to run
b
