X-Spam-Check-By: sourceware.org
Message-ID: <44A2E094.9070806@gmail.com>
Date: Wed, 28 Jun 2006 21:03:32 +0100
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
CC: David Mastronarde <mast AT colorado DOT edu>
Subject: Why is a file specified in DOS format opened in binary mode?
References: <Pine DOT LNX DOT 4 DOT 64 DOT 0606241421040 DOT 4607 AT druid DOT hvem DOT colorado DOT edu>  <449EF283 DOT 80500 AT gmail DOT com>  <Pine DOT LNX DOT 4 DOT 64 DOT 0606271119500 DOT 29629 AT druid DOT hvem DOT colorado DOT edu> <b88bb1ad0606271303v77fe3bf0w4a640cb6e3794d66 AT mail DOT gmail DOT com> <Pine DOT LNX DOT 4 DOT 64 DOT 0606271415110 DOT 29629 AT druid DOT hvem DOT colorado DOT edu>
In-Reply-To: <Pine.LNX.4.64.0606271415110.29629@druid.hvem.colorado.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
From: Dave <kilroyd AT googlemail DOT com>
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

(was Re: sed 4.1.5 adds extra CR with input file path in Windows format)

David Mastronarde wrote:
> On Tue, 27 Jun 2006, Dave Kilroy wrote:
>> On 6/27/06, David Mastronarde wrote:
>>> On Sun, 25 Jun 2006, Dave wrote:
>>>> David Mastronarde wrote:
>>>>> After upgrading sed from 4.1.4 to 4.1.5, I found that line endings were
>>>>> being converted from CRLF to CRCRLF when the input file was specified
>>>>> with a windows file path:
>>>> Have a read of http://cygwin.com/cygwin-ug-net/using-textbinary.html
>>>>
>>>> Try specifying the output file in MSDOS format, '.\sedtestout'.
>
> So it all makes sense in terms of it following the rules.  But I am 
> curious as to the reason for rule b.  Most things in Cygwin seem to deal 
> interchangeably with windows and cygwin paths.

Sorry, can't help you there - this behaviour has been present longer 
than I have monitorred this list. A google didn't bring much 
enlightenment either.

Anyone else?

Dave.

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