Freddy Vulto wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDIR='
Anders Kaseorg wrote:
> Bash Version: 4.0
> Patch Level: 33
> Release Status: release
>
> Description:
> With the globstar option enabled, bash seems to misinterpret
> other wildcard path components between a **/ and the last / as
> matching any path, even if the path doesn't ma
Even in the latest bash, 4.0.33, $() parsing is still broken:
$ bash -c 'echo $(echo \|)'
bash: -c: line 0: unexpected EOF while looking for matching `)'
bash: -c: line 1: syntax error: unexpected end of file
And yes, this is bash built with GNU bison, not Berkeley yacc.
--
Christian "naddy" We
Christian Weisgerber writes:
> Even in the latest bash, 4.0.33, $() parsing is still broken:
>
> $ bash -c 'echo $(echo \|)'
> bash: -c: line 0: unexpected EOF while looking for matching `)'
> bash: -c: line 1: syntax error: unexpected end of file
This has been fixed with patch 1, are you sure y
