Re: 5.3-alpha: the `jobs' builtin prints foreground dead jobs with function substitutions

2024-04-29 Thread Robert Elz
Date:Mon, 29 Apr 2024 16:07:26 -0400 From:Chet Ramey Message-ID: <11d627e9-174c-40a8-b827-0a2678d58...@case.edu> | So the question is what exactly constitutes a foreground job whose status | has "not been reported." I doubt it is stated anywhere, but I would

Re: 5.3-alpha: the `jobs' builtin prints foreground dead jobs with function substitutions

2024-04-29 Thread Chet Ramey
On 4/27/24 5:15 PM, Koichi Murase wrote: I'm currently testing my framework with 5.3-alpha. In 5.3-alpha and the devel branch, foreground dead jobs are reported by the `jobs' builtin with function substitutions: OK, let's explore this again. POSIX says `jobs' should report on "the status of

Re: 5.3-alpha: value substitutions remove unrelated REPLY when its REPLY is removed

2024-04-29 Thread Chet Ramey
On 4/27/24 5:43 PM, Koichi Murase wrote: When REPLY that is prepared by a value substitution ${ ; } is removed by , the value substitution removes the previous-scope REPLY, which is not prepared by the value substitution, after the execution of . $ bash-5.3-alpha --norc $ unlocal() { unset -v

Re: Bug#1069978: bash: incorrect value of $BASH for login shells

2024-04-29 Thread Chet Ramey
On 4/28/24 6:18 PM, Gioele Barabucci wrote: On 28/04/24 22:50, Chet Ramey wrote: On 4/28/24 3:07 PM, Gioele Barabucci wrote: $ su -l $USER -s /bin/bash-static -c 'echo $BASH; readlink /proc/$$/exe; head -1z /proc/$$/cmdline; echo' /bin/bash /usr/bin/bash-static