bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: `echo "#ls"` ik ok. But not `echo " #ls"`


From: Chet Ramey
Subject: Re: `echo "#ls"` ik ok. But not `echo " #ls"`
Date: Sun, 29 Oct 2006 13:15:41 -0500
User-agent: Thunderbird 1.5.0.7 (Macintosh/20060909)

Chacallot Chacallot wrote:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACH
> TYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown'
> -DLOCALEDIR='/usr/share/locale' -DPACKAGE='b
> ash' -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib   -g -O2
> uname output: Linux troppix 2.6.17.13-64 #1 Fri Oct 6 21:39:23 UTC
> 2006 x86_64 AMD Athlon(tm) 64 Pro
> cessor 3400+ AuthenticAMD GNU/Linux
> Machine Type: x86_64-unknown-linux-gnu
> 
> Bash Version: 3.2
> Patch Level: 0
> Release Status: release
> 
> Description:
> Hi!
> 
> So if I do `echo "#ls"` I get :
> bash: #ls: command not found
> Which is ok IMHO.
> 
> But If I do `echo " #ls"`
> I get $PS2 :

Patch 1 to bash-3.2 fixes this.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                       Live Strong.  No day but today.
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]