X-Spam-Check-By: sourceware.org
Message-ID: <860934040609271509r77f49c3br96a3b3ab51018b8e@mail.gmail.com>
Date: Wed, 27 Sep 2006 15:09:11 -0700
From: "Malcolm Nixon" <malcolm DOT nixon AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bash 3.1.17(8) CR/LF problem
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

mwoehlke wrote:
> Right; non-standard behavior (and any non-binary treatment
> of '\r' certainly counts!) should - and I might dare even to say
> "must" - be disabled by default. Although in this case I can't
> think of any reason why you would ever have a '\r' in a shell
> script (other than as part of a line ending). Although if we
> make any of this optional, then IMO it needs to be done the
> right way, which is to just ignore '\r', at least at the end of
> lines. That way we can ALWAYS read in binary mode, and
> it isn't a major performance penalty.

I guess I'm 50/50 here. On one hand <CR> is most certainly
not a standard line terminator character on Unix systems, but
at the same time Cygwin advertises a "collection of tools which
provide Linux look and feel" for Windows.

If pure Linux compatibility/restrictions was the only goal, then
it could be achieved far easier by running Debian in a VM.

Instead Cygwin tries to add the power of the Linux-like tools
into the cruftiness of Windows. Unfortunately I believe that implies
supporting Windows/DOS crufty CR/LF files.

--
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/