[bug #65651] argument reference inconsistency

URL: Summary: argument reference inconsistency Group: The GNU Bourne-Again SHell Submitter: None Submitted: Sun 28 Apr 2024 06:51:44 AM UTC Category: None Seve

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

Package: bash Version: 5.2.21-2 X-Debbugs-CC: bug-bash@gnu.org Hi, bash 5.0 and 5.2 do not set $BASH to the right value when bash is used as the login shell: $ apt install bash-static $ getent passwd $USER | cut -d: -f 7 /bin/bash $ su $USER -s /bin/bash-static -c 'echo $BASH

Re: bash: ":?xxx" filename broken on autocomplete

On Sat, 27 Apr 2024 23:56:28 +0200 Andreas Schwab wrote: > On Apr 27 2024, Kerin Millar wrote: > > > In the course of trying this in bash-5.3-alpha, I noticed something else. > > If ':?aa' is not the only entry in the current working directory, readline > > behaves as if : is an ambiguous comp

Re: bash: ":?xxx" filename broken on autocomplete

On Apr 27 2024, Kerin Millar wrote: > In the course of trying this in bash-5.3-alpha, I noticed something else. If > ':?aa' is not the only entry in the current working directory, readline > behaves as if : is an ambiguous completion. That is: > > # mkdir ':?aa' > # touch 'something-else' > # rm

Re: bash: ":?xxx" filename broken on autocomplete

On Sat, 27 Apr 2024 23:28:49 +0200 Gioele Barabucci wrote: > Control: found -1 5.2.21-2 > > On Tue, 27 Aug 2019 16:36:03 +0200 Philipp Marek > wrote: > > the autocompletion is broken on filenames or directories with ":?" at the > > beginning. > > > > # mkdir ':?aa' > > # rmdir : > >

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

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 "$@"; } $ f2() { unlocal "$1"; echo "f2:$1=${

Re: bash: ":?xxx" filename broken on autocomplete

Control: found -1 5.2.21-2 On Tue, 27 Aug 2019 16:36:03 +0200 Philipp Marek wrote: the autocompletion is broken on filenames or directories with ":?" at the beginning. # mkdir ':?aa' # rmdir : gives me # rmdir :\:\? which doesn't match the filename; I can finish completion by

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

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: $ bash-5.3-alpha --norc $ a=${ (true) }; b=${ jobs; }; declare -p b declare -- b="[1] Done( true )" I ex

Re: Examples of concurrent coproc usage?

On Mon, 22 Apr 2024, Martin D Kealey wrote: On Mon, 22 Apr 2024, 09:17 Carl Edquist, wrote: […] I was saying the shell is crippled when limited to builtins; eg, a read/printf loop compared to simply running cat. I would hope that mapfile/readarray could do better, since it's not obligated

Re: Examples of concurrent coproc usage?

On Mon, 22 Apr 2024, Chet Ramey wrote: You might be surprised. The OP was sending thousands of calculations to (I think) GNU bc, which had some resource consumption issue that resulted in it eventually hanging, unresponsive. The kill was the solution there. I imagine there are similar scenar

Re: Linux reports memfd_create() being called without MFD_EXEC or MFD_NOEXEC_SEAL set

On Sat, 27 Apr 2024 14:09:29 +0200 Andreas Schwab wrote: > On Apr 27 2024, Kerin Millar wrote: > > > At some point after upgrading to bash-5.3-alpha, the following message > > appeared in my kernel ring buffer. > > > > [700406.870502] bash[3089019]: memfd_create() called without MFD_EXEC or >

Re: Linux reports memfd_create() being called without MFD_EXEC or MFD_NOEXEC_SEAL set

On Apr 27 2024, Kerin Millar wrote: > At some point after upgrading to bash-5.3-alpha, the following message > appeared in my kernel ring buffer. > > [700406.870502] bash[3089019]: memfd_create() called without MFD_EXEC or > MFD_NOEXEC_SEAL set This warning has been tuned down in later kernels,

Linux reports memfd_create() being called without MFD_EXEC or MFD_NOEXEC_SEAL set

Hi, At some point after upgrading to bash-5.3-alpha, the following message appeared in my kernel ring buffer. [700406.870502] bash[3089019]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set Unfortunately, it took me a while to notice the presence of this message. Therefore, I am