This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
bash builtin "echo" default behaviour wrong?
- To: gnu-win32 at cygnus dot com
- Subject: bash builtin "echo" default behaviour wrong?
- From: ads at rmbmain dot rmb dot co dot za
- Date: Fri, 19 Dec 97 19:44:53 SAST
Hi,
How do I change to default behaviour of the bash builtin "echo" command to
process the backslash-escape?
bash-2.01$ echo "first \n next"
first \n next
bash-2.01$ echo -e "First \n next"
bash-2.01$ echo -e "first \n next"
first
next
bash-2.01$
bash --posix does not help.
I know I can use an alias or a function, but why is this different from the
Bourne Shell (/bin/sh) and Korn Shell) (/bin/ksh) and /bin/echo
Thanks
Alberto da Silva
ads@rmb.co.za
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".