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
X-Authentication-Warning:	moscow.cs.rochester.edu: jkramer owned process doing -bs
Date:	Fri, 18 Jun 2004 12:33:20 -0400 (EDT)
From:	John Kramer <jkramer AT cs DOT rochester DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	Carriage Returns
Message-ID:	<Pine.LNX.4.44.0406181231570.1164-100000@moscow.cs.rochester.edu>
MIME-Version:	1.0

To whom it may concern:

I have a real problem with the way that cygwin/cygwin's version of perl 
handles carriage returns (\r).  I was working on a program in perl on 
cygwin which takes input from files.  I stripped newlines from the input, 
and then found that the strings that I stripped newlines from suddenly 
would print on top of other strings when I printed them.  Eventually I 
figured out that cygwin takes the carriage return *literally*.  It really 
goes back to the beginning of the same line if there is no newline.  Does 
that really make sense?  Shouldn't it just treat the carriage return as a 
newline?  I ran the same program with the (dos formatted) input files on a 
redhat linux machine.  The carriage returns are completely ignored (which 
would be reasonable behavior for cygwin, too).  If there are good reasons 
for the way cygwin handles carriage returns, let me know.  Else, I suggest 
that you change this behavior for the next release.

Thanks,
John


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

- Raw text -