Re: Minor mistake in Bash manual

2019-03-12 Thread Todd Lehman
On Tue, 12 Mar 2019, Chet Ramey wrote: On 3/11/19 4:55 PM, Todd Lehman wrote: Hi! In the version dated 2019-Jan-07, I noticed the following mistake in the GNU Bash manual: | Associative arrays are created using | declare -A name. The period (".") after "name" should not be there. Is this th

Re: Minor mistake in Bash manual

2019-03-12 Thread Chet Ramey
On 3/11/19 4:55 PM, Todd Lehman wrote: > Hi! > > In the version dated 2019-Jan-07, I noticed the following mistake in the > GNU Bash manual: > > | Associative arrays are created using > | declare -A name. > > The period (".") after "name" should not be there. Is this the man page or the texinfo

One Crash per Log-in Caused by: echo '' > >(echo)

2019-03-12 Thread jake
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/loc

Re: Bug: Bash forgets sourcefile and linenumber of read-in functions

2019-03-12 Thread Greg Wooledge
On Mon, Mar 11, 2019 at 02:26:20PM -0700, L A Walsh wrote: > How would that break compatibility? The same way shellshock did. A function exported by a parent bash process using format A could not be read by a child bash process expecting format B. Now, you may be thinking, "This makes no sense!