Re: Behavior change

On 10/27/20 10:10 AM, Gregory Heytings wrote: > >>> Okay.  I just set "set enable-bracketed-paste off" in my /etc/inputrc. >>> Perhaps this change should be documented in CHANGES, and in the man page >>> (where enable-bracketed-paste is said to have the default value Off). >> >> The manual page in

Re: Behavior change

Okay.  I just set "set enable-bracketed-paste off" in my /etc/inputrc. Perhaps this change should be documented in CHANGES, and in the man page (where enable-bracketed-paste is said to have the default value Off). The manual page in the released version will reflect the default setting of

Re: Behavior change

On 10/27/20 9:55 AM, Gregory Heytings wrote: > > Okay.  I just set "set enable-bracketed-paste off" in my /etc/inputrc. > Perhaps this change should be documented in CHANGES, and in the man page > (where enable-bracketed-paste is said to have the default value Off). The manual page in the releas

Re: Behavior change

Hi Chet, Thanks for your reply! I just installed Bash 5.1 rc1.  I have IGNOREEOF set, and in 5.0 (and earlier version) when pressing C-d one sees: $ Use "logout" to leave the shell. With 5.1 rc1 there is a newline between the prompt and the message: $ Use "logout" to leave the shell. Is

Re: Behavior change

On 10/26/20 5:58 PM, Gregory Heytings via Bug reports for the GNU Bourne Again SHell wrote: > > Hi, > > I just installed Bash 5.1 rc1.  I have IGNOREEOF set, and in 5.0 (and > earlier version) when pressing C-d one sees: > > $ Use "logout" to leave the shell. > > With 5.1 rc1 there is a newline

Behavior change

Hi, I just installed Bash 5.1 rc1. I have IGNOREEOF set, and in 5.0 (and earlier version) when pressing C-d one sees: $ Use "logout" to leave the shell. With 5.1 rc1 there is a newline between the prompt and the message: $ Use "logout" to leave the shell. Is this change intentional? Tha

Re: bang-hash behavior change?

On 2/25/15 7:40 PM, Milo H. Fields wrote: > Greetings, > > I noticed that the ‘bang-hash’ behavior seems to have changed somewhere > between bash version 4.1.17 and 4.3.33. > > > > e.g. for the script ‘jnk’ containing: > > echo "plain: !#" > echo " parens: ${!#}" It changed for Posix mode b

Re: bang-hash behavior change?

On Wed, Feb 25, 2015 at 07:40:07PM -0500, Milo H. Fields wrote: > echo " parens: ${!#}" > bash 4.1.17: > > $ sh jnk arg1 arg2 > > plain: !# > > parents: arg2 Can't say I've ever seen this syntax before. It looks like you are trying to get the last argument. The syntax I've seen for getting

Re: bang-hash behavior change?

On Thu, Feb 26, 2015 at 2:40 AM, Milo H. Fields wrote: > Greetings, > > I noticed that the 'bang-hash' behavior seems to have changed somewhere > between bash version 4.1.17 and 4.3.33. > > > > e.g. for the script 'jnk' containing: > > echo "plain: !#" > > echo " parens: ${!#}" > > > > bash 4.3.

Behavior change/feature : display -p var; where var is a "placeholder" variable

"Placeholder" variables currently can be displayed if they have an attribute (iaArn) (1). Could there be a consideration for a behavior change/feature to display them by name and prefix (2)(3)? For illustration purposes: 1) declare -i var; declare -pi 2) declare -i var; declare -

Re: 4.3 compgen behavior change (quoted arg)

On 2/13/13 5:46 AM, Raphaël Droz wrote: > I'm not sure whether or not this is to be expected. > > $ echo $BASH_VERSION > 4.2.42(1)-release > $ touch a.log > $ compgen -f -X '!*.log' -- \'\' > $ > > > $ echo $BASH_VERSION > 4.3.0(3)-devel > $ touch a.log > $ compgen -f -X '!*.log' -- \'\' > a.l

4.3 compgen behavior change (quoted arg)

I'm not sure whether or not this is to be expected. $ echo $BASH_VERSION 4.2.42(1)-release $ touch a.log $ compgen -f -X '!*.log' -- \'\' $ $ echo $BASH_VERSION 4.3.0(3)-devel $ touch a.log $ compgen -f -X '!*.log' -- \'\' a.log $ This kind of "quoted" call is used by bash-completion _filedi