Re: echo(1) non-conformant (processing -e and -E)

2007-11-26 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Rich Felker on 11/26/2007 8:51 PM: > POSIX leaves behavior unspecified when -n is the first argument, and > also when any argument contains backslashes. However, if conformance > to the XSI part of SUSv3 is also desired, -e must be default

echo(1) non-conformant (processing -e and -E)

2007-11-26 Thread Rich Felker
When running in POSIX/sh mode, bash should either disable the echo builtin or stop giving special treatment to -e and -E. In particular, POSIX provides well-defined behavior for: echo -e bash gives: blank line posix gives: line containing only "-e" echo -E bash gives: blank line posix gives: line