This is the mail archive of the
mailing list for the cygwin project.
Re: igncr vs text mode mounts, performance vs compatibility
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Fri, 27 Oct 2006 10:45:12 -0400
- Subject: Re: igncr vs text mode mounts, performance vs compatibility
- References: <000701c6f95f$5300ab80$020aa8c0@DFW5RB41> <45415BDD.email@example.com> <45420DD3.firstname.lastname@example.org>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On Fri, Oct 27, 2006 at 09:46:59AM -0400, Jonathan Arnold wrote:
>Eric Blake wrote:
>>-----BEGIN PGP SIGNED MESSAGE-----
>>According to Gary R. Van Sickle on 10/26/2006 6:31 PM:
>>> My question was, to paraphrase, "Why would anybody want
>>>the old, broken behavior?"
>>Because it is identical to the behavior you would get for the same script
>>on Linux. Cygwin emulates Linux, and until Linux ignores \r on binary
>>files, you should not expect cygwin to go out of its way to do so either.
>BTW, I would like to add my voice to the silent majority who is very very
>happy to have Linux compatibility maintained. I use bash scripts on both
>Linux & Cygwin and have in the past run into line ending problems. It's as
>mysterious on Linux as it has proven to be on Cygwin. Having them both
>behave identically is the correct path, IMHO. And while I consider your
>efforts to ease the pain on the Windows side, I also appreciate how you
>are sticking to your guns on this matter.
Number of messages from people who understand the 2
issue and are appreciative.