> Can we easily get cat>foo (or some equivalent) to produce CRLF files?
I guess I meant, "can we get cat>foo (or some equivalent)" to produce
CRLF files *when hello does*. That is, to get some standard command to
operate in text mode under mingw[/cygwin/whatever]. Does echo also
operate in b
Hello Karl,
* Karl Berry wrote on Mon, Aug 28, 2006 at 08:31:37PM CEST:
> > However, on MinGW all three tests fail because the program outputs CRLF
> > line endings, while the test suite creates files with LF ending.
>
> Um, why? That is, why does cat>foo produce LF files while hello>foo
> However, on MinGW all three tests fail because the program outputs CRLF
> line endings, while the test suite creates files with LF ending.
Um, why? That is, why does cat>foo produce LF files while hello>foo
produces CRLF files?
Is this different in MinGW than under Cygwin? (I'm probab
Karl Berry wrote:
> Or produce output with CR/LF always,
>
> Really? That seems wrong to me for Hello (and just about any other
> program). Just running hello on a Unixish system shouldn't write a \r!
Not on Unix systems, of course. But on Woe32 systems, writing text with
CR/LF is the norm
Some programs, which produce output from given input
Ack.
accept a --binary option
Ick.
Or produce output with CR/LF always,
Really? That seems wrong to me for Hello (and just about any other
program). Just running hello on a Unixish system shouldn't write a \r!
have the te
Karl Berry wrote:
> However, on MinGW all three tests fail because the program outputs CRLF
> line endings, while the test suite creates files with LF ending.
> (Not sure if you want to worry about this...)
>
> Not sure if I do either. What do other (real) programs do?
Some programs
