binary mode from non-Cygwin shells?

[Christopher Faylor]

On Wed, Nov 29, 2000 at 08:47:24AM -0800, Earnie Boyd wrote:
>--- Malcolm Boekhoff <Malcolm.Boekhoff@actfs.co.uk> wrote:
>> > Nevertheless:
>> >
>> > > You will find that if you set CYGWIN=nobinmode before executing your
>> > > command.com example od will read in text mode and the \r will be
>> eliminated.
>> > > Or, if you use the echo executable found in the Cygwin/bin directory
>> instead of
>> > > the shell builtin the \r will not be written.
>> >
>> > Nope.  If I leave CYGWIN unset, and run the Cygwin echo.exe explicitly:
>> >
>> > d:\users\antony>c:\cygwin\bin\echo.exe hello |od -c
>> > 0000000000     h   e   l   l   o  \r  \n
>> > 0000000007
>> >
>> 
>> Is this because the pipe is being created by command.com and not bash?
>> 
>
>The documentation is correct.  The [no]binmode was created by Chris
>specifically for executing Cygwin programs in the command.com/cmd.exe shell. 
>The default should be binmode.  But, I may be the one confused.

We changed the default some time ago at the request of an, er, customer
who was distressed at seeing files with \n's and no \r\n's.

Pipes have nothing to do with this.  The standard output of a program
is controlled by the CYGWIN=[no]binmode setting when the program is
run outside of a cygwin environment.

Undoubtedly the documentation has not been updated to reflect this.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com