On 9/28/12 9:54 AM, Yuxiang Cao wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i486
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_V$
> un
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_V$
uname output: Linux frank-laptop 2.6.32-42-generic #96-
On Fri, Sep 28, 2012 at 12:52 AM, wrote:
> [OT] Thanks for your work for the Bash project. I've just learned that you've
> been the main maintainer for a long time, so keep it up! :)
+1000 to that, bash makes my life so much easier and I doubt you get
enough thanks
On 9/28/12 12:52 AM, hans1wo...@gmail.com wrote:
>> The question is whether or not !(x) should match the empty string. The
>> bash matcher treats it similarly to [!x], which does not.
>
> It does however match the empty string at most times. So I guess that's the
> real bug. Again, there is some
Configuration Information [Manually filled]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: //
uname output: Linux debianBunker 2.6.26-pentium4 #11 Fri Jul 20 10:03:38 CEST
2012 i686 GNU/Linux
Machine Type: i486-pc-linux-gnu
Bash Version: 4.2.0(5)-release (i686-pc-linux-gnu)
Descr