From: R I Feigenblatt <docdtv@earthlink.net>
To: gnu-win32@cygnus.com
Subject: echo fails to behave and documented
Date: Sat, 06 Mar 1999 12:06:00 -0000 [thread overview]
Message-ID: <3.0.2.32.19990306150608.007baec0@mail.earthlink.net> (raw)
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!
Ron Feigenblatt
*** ENCLOSURE FOLLOWS (Cygwin Beta 20.1 on Win 98) ***
BASH.EXE-2.02$ echo -ne Line1\\012Line2> E:\\test.txt
E:\>dir 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
E:\>debug test.txt
-d
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).
Ron Feigenblatt
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: R I Feigenblatt <docdtv@earthlink.net>
To: gnu-win32@cygnus.com
Subject: echo fails to behave and documented
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <3.0.2.32.19990306150608.007baec0@mail.earthlink.net> (raw)
Message-ID: <19990331194500.9fLEYpf8adYnEKZHgaWiix9E4PHV5bcOwjj3D47OpBA@z> (raw)
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!
Ron Feigenblatt
*** ENCLOSURE FOLLOWS (Cygwin Beta 20.1 on Win 98) ***
BASH.EXE-2.02$ echo -ne Line1\\012Line2> E:\\test.txt
E:\>dir 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
E:\>debug test.txt
-d
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).
Ron Feigenblatt
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-03-06 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-06 12:06 R I Feigenblatt [this message]
1999-03-31 19:45 ` R I Feigenblatt
1999-03-07 3:18 R I Feigenblatt
1999-03-31 19:45 ` R I Feigenblatt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.2.32.19990306150608.007baec0@mail.earthlink.net \
--to=docdtv@earthlink.net \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).