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@cygwin.com CC: David Mastronarde Subject: Why is a file specified in DOS format opened in binary mode? References: <449EF283.80500@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Dave Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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/