Re: hyphens (-) and underscores (_) are not treated as equivalent with completion-map-case and completion-ignore-case enabled

2021-01-20 Thread awa54
On 2021-01-19 22:32, Chet Ramey wrote: On 1/19/21 8:30 AM, aw...@cdak.net wrote: Bash Version: 5.1 Patch Level: 4 Release Status: release Description: man bash says:  > completion-map-case (Off)  > If set to On, and completion-ignore-case is enabled, readline treats hyphens (-) and underscor

${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Oğuz
$ declare -l a $ echo "${a:=X} $a" X x This doesn't jive with what the manual says. `-l`: > When the variable is assigned a value, all upper-case characters are converted to lower-case. `:=`: > If parameter is unset or null, the expansion of word is assigned to parameter. The value o

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Léa Gris
Le 20/01/2021 à 12:16, Oğuz écrivait : $ declare -l a $ echo "${a:=X} $a" X x This doesn't jive with what the manual says. `-l`: When the variable is assigned a value, all upper-case characters are converted to lower-case. `:=`: If parameter is unset or null, the expansion of

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Andreas Schwab
On Jan 20 2021, Léa Gris wrote: >> The value of parameter is then substituted. > > The expansion part: > The value X is expanded but is not affected by the lowercase > transformation flag from a, so it remains as X. But that's not the value of the parameter. Andreas. -- Andreas Schwab, sch...@

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Léa Gris
Le 20/01/2021 à 13:51, Andreas Schwab écrivait : But that's not the value of the parameter. It is not, since at this point, the parameter has no value, the expansion expands the argument's value after ;= which is uppercase X here. -- Léa Gris

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Andreas Schwab
On Jan 20 2021, Léa Gris wrote: > Le 20/01/2021 à 13:51, Andreas Schwab écrivait : >> But that's not the value of the parameter. > > It is not, since at this point, the parameter has no value, That is not true. Otherwise the expansion would be empty. > the expansion expands the argument's value

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Oğuz
20 Ocak 2021 Çarşamba tarihinde Léa Gris yazdı: > Le 20/01/2021 à 12:16, Oğuz écrivait : > >> $ declare -l a >> $ echo "${a:=X} $a" >> X x >> >> This doesn't jive with what the manual says. >> >> `-l`: >> >>> When the variable is assigned a value, all upper-case characters are >>>

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Chet Ramey
On 1/20/21 6:16 AM, Oğuz wrote: $ declare -l a $ echo "${a:=X} $a" X x This doesn't jive with what the manual says. `-l`: When the variable is assigned a value, all upper-case characters are converted to lower-case. `:=`: If parameter is unset or null, the expansion of word i

Re: ${a:=b} expands to `b', not `a''s value

2021-01-20 Thread Oğuz
On Wed, Jan 20, 2021 at 6:44 PM Chet Ramey wrote: > Thanks for the report. It's probably not what you intend, but it's the way > bash has done things all the way back to bash-4.0 when the additional > variable attributes were introduced (and further back if you consider the > integer attribute).