Re: An array variable created by export/readonly builtins inside a function becomes a locale variable to that function unexpectedly

2015-12-05 Thread Chet Ramey
On 11/27/15 10:18 PM, ziyunfei wrote: > $ ksh -c 'foo() { readonly a=(1);echo a=$a; }; foo; echo a=$a' > a=1 > a=1 > $ bash -c 'foo() { readonly a=(1);echo a=$a; }; foo; echo a=$a' # a becomes a > local variable > a=1 > a= Thanks for the report. I agree that this is a bug. `readonly' and `expor

Re: Random parser error of $() when there is a case inside

2015-12-05 Thread Chet Ramey
On 12/4/15 1:25 PM, Luiz Angelo Daros de Luca wrote: > Bash Version: 4.2 > Patch Level: 53 > Release Status: release > > Description: > While writing a script, I faced a random parser error with code like > > A=$( > ... > case b in > c) > ... > esac > ... > ) > > Minor changes like renaming a

Re: Out of bounds heap read in function rl_tilde_expand

2015-12-05 Thread Hanno Böck
On Mon, 9 Nov 2015 09:57:22 -0500 Chet Ramey wrote: > On 11/6/15 9:46 AM, Hanno Böck wrote: > > While testing bash with address sanitizer I discovered a heap out of > > bounds read. This affects bash 4.3 with the latest patchlevel 42. > > Thanks for the report. This will be fixed in the next

Re: Out of bounds heap read in function rl_tilde_expand

2015-12-05 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/5/15 4:12 PM, Hanno Böck wrote: > On Mon, 9 Nov 2015 09:57:22 -0500 > Chet Ramey wrote: > >> On 11/6/15 9:46 AM, Hanno Böck wrote: >>> While testing bash with address sanitizer I discovered a heap out of >>> bounds read. This affects bash 4.3 w

Re: Installation of PDF/PS/DVI and HTML files

2015-12-05 Thread Chet Ramey
On 12/3/15 6:05 AM, Ludovic Courtès wrote: > Hello, > > Akira of Debian noticed that ‘make all’ rebuilds and install > PDF/PS/DVI/HTML documentation by default, which prevents default Bash > builds from being bit-reproducible¹. This isn't completely accurate, since `make all' doesn't install anyt

[POSIX] `a='a b'; export a=$a; echo $a` gives `a b` instead of `a`

2015-12-05 Thread Mingye Wang (Arthur2e5)
Bash Version: 4.3 Patch Level: 42 Release Status: Release Description: According to [POSIX.1], `export` is special builtin *command*. Therefore as a command, in `a='a b'; export a=$a; echo $a`, `$a` should get split into words `a` and `b`. However, `bash` takes this as `export 'a=a b'` and gi

Re: Script shell suspends after executing second child process

2015-12-05 Thread konsolebox
On Sun, Nov 15, 2015 at 2:25 PM, konsolebox wrote: > On Sun, Nov 15, 2015 at 10:34 AM, Chet Ramey wrote: >> On 11/14/15 6:02 PM, Chet Ramey wrote: >> >> Here, try this patch. It sort of splits the difference along the lines of >> your suggestion, and it behaves correctly for the case that inspir

Re: Installation of PDF/PS/DVI and HTML files

2015-12-05 Thread Chet Ramey
On 12/4/15 4:24 AM, Ludovic Courtès wrote: > Greg Wooledge skribis: > >> On Thu, Dec 03, 2015 at 01:08:13PM +0200, Ludovic Courtès wrote: >>> Given that the GCS suggests installing only the Info version of the >>> manual by default (info "(standards) Standard Targets") >> >>> What do you think? >

Re: [POSIX] `a='a b'; export a=$a; echo $a` gives `a b` instead of `a`

2015-12-05 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/5/15 6:57 PM, Mingye Wang (Arthur2e5) wrote: > Bash Version: 4.3 > Patch Level: 42 > Release Status: Release > > Description: > According to [POSIX.1], `export` is special builtin *command*. > Therefore as a command, in `a='a b'; export a=$a;

bash variable names do not comply w/POSIX character set rules

2015-12-05 Thread Linda Walsh
Under section 2.5.3, Shell Variables, it mentions: LC_CTYPE Determine the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters), which characters are defined as letters (character class alpha) and characters (chara