bug-bash
[Top][All Lists]
Advanced

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

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


From: Chacallot Chacallot
Subject: `echo "#ls"` ik ok. But not `echo " #ls"`
Date: Sat, 28 Oct 2006 19:23:55 +0000

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 :


So am not sure if this is a feature or a bug... Or maybe I completly
miss the point..

But what's sure is that under a bash 3.0.16 both commands returns the
same thing : bash: #ls: command not found.

And gstreamer is using a line like this in its ./common/m4/as-scrub-include.m4
GIVEN_CFLAGS=`echo $GIVEN_CFLAGS | sed -e "s#-I$dir ##"`
And it fails using bash 3.2.

Unless I did something else wrong while building my CLFS...

Regards,
Chacallot.




reply via email to

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