Equivalence classes handled differently in mb vs non-mb patterns

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnux32 Compiler: gcc-10.1.0 -mx32 Compilation CFLAGS: -O2 -Wno-parentheses -Wno-format-security uname output: Linux loucetios 5.7.9 #1 SMP @1590968955 x86_64 GNU/Linux Machine Type: x86_64-pc-linux-gnux32

Re: apparent inconsistencies in readline documentation

On 27/7/20 22:09, Chet Ramey wrote: > On 7/25/20 12:21 PM, Daniel Molina wrote: >> Hi, >> >> I found some aspects of readline documentation that seem inconsistent to >> me and I wanted to share them. >> >> 1. The difference between backward-kill-line and unix-line-discard >> readline commands. >> >

warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp'

Hi, On Ubuntu 20.04, I try to compile the git master version of bash with the followin steps: $ sudo apt-get build-dep bash $ git clone https://git.savannah.gnu.org/git/bash.git bash.git $ cd bash.git $ ./configure $ make -j44 [...] /usr/bin/ld: ./lib/sh/libsh.a(tmpfile.o): in function `sh_mktmpn

`help declare' don't show the same document with the online one.

Hi, On Ubuntu 20.04, I installed the latest git master version of bash. Then I check the document for declare built-in command and also check the online document located here: https://www.gnu.org/software/bash/manual/bash#Bash-Builtins. The online version of the document for declare told the foll

Re: warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp'

On 7/28/20 8:19 AM, Hongyi Zhao wrote: > Hi, > > On Ubuntu 20.04, I try to compile the git master version of bash with > the followin steps: > > $ sudo apt-get build-dep bash > $ git clone https://git.savannah.gnu.org/git/bash.git bash.git > $ cd bash.git > $ ./configure > $ make -j44 > [...] > /

Re: `help declare' don't show the same document with the online one.

> The online version of the document for declare told the following usage: > > > declare > declare [-aAfFgilnrtux] [-p] [name[=value] …] > [...] > The -p option will display the attributes and values of each name. > When -p is used with name arguments, additional options, other than -f > and -F

Re: apparent inconsistencies in readline documentation

On 7/28/20 4:21 AM, Daniel Molina wrote: > On 27/7/20 22:09, Chet Ramey wrote: >> On 7/25/20 12:21 PM, Daniel Molina wrote: >>> Hi, >>> >>> I found some aspects of readline documentation that seem inconsistent to >>> me and I wanted to share them. >>> >>> 1. The difference between backward-kill-lin

Re: No word splitting for assignment-like expressions in compound assignment

On 7/23/20 8:11 PM, Alexey Izbyshev wrote: > Hello! > > I have a question about the following behavior: > > $ Z='a b' > $ A=(X=$Z) > $ declare -p A > declare -a A=([0]="X=a b") > $ A=(X$Z) > $ declare -p A > declare -a A=([0]="Xa" [1]="b") > > I find it surprising that no word splitting is perfo

Re: `help declare' don't show the same document with the online one.

On Tue, Jul 28, 2020 at 9:25 PM Chet Ramey wrote: > > > > The online version of the document for declare told the following usage: > > > > > > declare > > declare [-aAfFgilnrtux] [-p] [name[=value] …] > > [...] > > The -p option will display the attributes and values of each name. > > When -p is u

Re: No word splitting for assignment-like expressions in compound assignment

On 28.7. 17:22, Chet Ramey wrote: On 7/23/20 8:11 PM, Alexey Izbyshev wrote: $ Z='a b' $ A=(X=$Z) $ declare -p A declare -a A=([0]="X=a b") It's an assignment statement in a context where assignment statements are accepted (which is what makes it different from `echo X=$Z', for instance), but

Re: No word splitting for assignment-like expressions in compound assignment

On 7/28/20 4:14 PM, Ilkka Virta wrote: > On 28.7. 17:22, Chet Ramey wrote: >> On 7/23/20 8:11 PM, Alexey Izbyshev wrote: >>> $ Z='a b' >>> $ A=(X=$Z) >>> $ declare -p A >>> declare -a A=([0]="X=a b") > >> It's an assignment statement in a context where assignment statements are >> accepted (which

Bug Report concerning backslash in bash5

Hello GNU team, I found this misbehaviour in Bash 5 (e.g. GNU bash, version 5.0.16(1)-release (x86_64-pc-linux-gnu)): $ BLA="1\.2"; echo 'x/'$BLA'/y/' \x/1\.2/\y/ I don't see any reasonable reason for the generated backslashes here. Compare to bash 4 (e.g. GNU bash, version 4.4.12(1)-release

Re: Bug Report concerning backslash in bash5

Ralph Beckmann writes: > I found this misbehaviour in Bash 5 (e.g. GNU bash, version > 5.0.16(1)-release (x86_64-pc-linux-gnu)): > > $ BLA="1\.2"; echo 'x/'$BLA'/y/' > \x/1\.2/\y/ > > I don't see any reasonable reason for the generated backslashes here. My guess is that you're running into the f

Re: Bug Report concerning backslash in bash5

On 7/29/20 1:35 AM, Dale R. Worley wrote: > Ralph Beckmann writes: >> I found this misbehaviour in Bash 5 (e.g. GNU bash, version >> 5.0.16(1)-release (x86_64-pc-linux-gnu)): >> >> $ BLA="1\.2"; echo 'x/'$BLA'/y/' >> \x/1\.2/\y/ >> >> I don't see any reasonable reason for the generated backslashe