echo fails to behave and documented
R I Feigenblatt
Sat Mar 6 12:06:00 GMT 1999
How come *** echo *** does NOT work as documented? (See below.)
Why is octal 012 changed to the two-character sequence CR-LF?
Yeah, I know DOS/Windows likes CR-LF.
Please change behaviour or docs!
*** ENCLOSURE FOLLOWS (Cygwin Beta 20.1 on Win 98) ***
BASH.EXE-2.02$ echo -ne Line1\\012Line2> E:\\test.txt
Volume in drive E is whatever
Volume Serial Number is whatever
Directory of E:\
TEST TXT 12 03-06-99 2:53p test.txt
1 file(s) 12 bytes
1168:0100 4C 69 6E 65 31 0D 0A 4C-69 6E 65 32 00 00 00 00 Line1..Line2....
BASH.EXE-2.02$ help echo
echo: echo [-neE] [arg ...]
Output the ARGs. If -n is specified, the trailing newline is
suppressed. If the -e option is given, interpretation of the
following backslash-escaped characters is turned on:
\num the character whose ASCII code is NUM (octal).
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin