Re: Builtin command echo does not work properly.

[Chet Ramey]

Christoph Jeksa wrote:
> From: Christoph_Jeksa@CoCreate.com
> To: bug-bash@gnu.org
> Subject: Builtin command echo does not work properly.
> 
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: cygwin
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin'
> -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
> -DSHELL -DHAVE_CONFIG_H -DRECYCLES_PIDS   -I.  -I/tmp/bash-3.1
> -I/tmp/bash-3.1/include -I/tmp/bash-3.1/lib   -O2
> uname output: Windows_NT d10lt014 1.5.19(0.150/4/2) 2006-01-20 13:28
> i686 Cygwin
> Machine Type: i686-pc-cygwin
> 
> Bash Version: 3.1
> Patch Level: 17
> Release Status: release
> 
> Description:
>         The builtin command echo [-neE] [arg ...] does not work properly
> 
> Repeat-By:
>         Enter:
>         echo -E "\ttext"
>         Expected result:
>         \ttext
>         Result:
>         -E      text

When in posix mode, if the `xpg_echo' option is enabled, bash behaves as
the POSIX standard specifies.  The standard disallows all options and
does not offer a way to disable backslash-escape interpretation.

Bash enters posix mode automatically when invoked as `sh'.  There is a
configuration option that enables the xpg_echo option automatically;
that's probably the case with the version you're using.

Chet

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