X-Spam-Check-By: sourceware.org
Message-ID: <453EA9C1.8060402@byu.net>
Date: Tue, 24 Oct 2006 18:03:13 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: igncr vs text mode mounts, performance vs compatibility
References: <1160655422743 DOT antti DOT nospam DOT 1605718 DOT wGO_WJ9D1NlId3tB-z6Qig AT luukku DOT com> <20061012123406 DOT GA30908 AT trixie DOT casa DOT cgf DOT cx> <452EA386 DOT 9010201 AT qualcomm DOT com> <20061012212011 DOT GA8535 AT trixie DOT casa DOT cgf DOT cx> <452EFDDB DOT 1010301 AT qualcomm DOT com> <452F8719 DOT 9060300 AT cygwin DOT com> <4536BC88 DOT 3030003 AT qualcomm DOT com> <4536C922 DOT 4090807 AT qualcomm DOT com> <45376CBF DOT 1030104 AT byu DOT net> <loom DOT 20061024T205240-509 AT post DOT gmane DOT org>
In-Reply-To: <loom.20061024T205240-509@post.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Lewis Hyatt on 10/24/2006 12:57 PM:
> Just a thought, it would probably solve 99% of people's problems if you just
> specified that if the first line of the script ends in \r\n, then \r will be
> ignored for the rest of the file. Then you would just need to read the first
> line a byte at a time, and every subsequent line could be read efficiently
> whenever possible, right? And it seems unlikely that this could possibly break
> anything.

Propose a patch, and I will consider it.  In my opinion, it was much
easier to do igncr as an all or none option than it was to parse the first
line and discard \r on a per-file basis, not to mention that all-or-none
is easily configurable so that those of us who WANT literal \r as required
by POSIX can do so.  To date, I have been the only person proposing
patches in the area of \r\n handling, rather than just ideas (which is
probably why I am the maintainer of the cygwin bash port).  And I have no
personal interest in redoing this patch to a more complex algorithm at
this time.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFPqk884KuGfSFAYARAvGAAJ9FSIRGBQlf/scMHFle+dR59NsnZwCgwgHQ
LqtTw7GlAnOllAcAHnmowI4=
=DY8g
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/