Difference of extglob between 5.0.0(1)-release and 4.4.23(1)-release

See the following for the difference. I'd consider the behavior of 4.4.23 should be correct. How was this bug introduced? Should there be a test case to cover this case? $ cat main_debug.sh #!/usr/bin/env bash # vim: set noexpandtab tabstop=2: echo $BASH_VERSION declare -- null="@()" declare --

Re: Probable recursion in particular alias

On 1/10/19 1:30 AM, Ante Perić wrote: > zrak:~ synthmeat$ bash --version > GNU bash, version 5.0.0(1)-release (x86_64-apple-darwin18.2.0) > Copyright (C) 2019 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software;

Re: Maybe a potential memory leak

On 1/5/19 1:32 AM, jr89...@hotmail.com wrote: > Bash Version: 4.2 > Patch Level: 46 > Release Status: release > > Description: > Some library built as shared library and the unit test programs will be > compiled into a script instead of binary file. Thanks for the report. There's not enough

Maybe a potential memory leak

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/locale'

Re: Sourcing a script from a pipe is not reliable

Yes, exactly. It appears that "source" tries to read from /dev/stdin before anything is ready from the pipe and treats that as an EOF. You do not even need to sleep, you can just use "cat" instead of "echo" to produce the script and "source" fails reliably. This appears to have been fixed in bash