X-Spam-Check-By: sourceware.org
Message-ID: <452BE676.1050109@tlinx.org>
Date: Tue, 10 Oct 2006 11:29:10 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bash and CR/LF line-endings
References: <4C89134832705D4D85A6CD2EBF38AE0F7B1342 AT PAUMAILU03 DOT ags DOT agere DOT com>
In-Reply-To: <4C89134832705D4D85A6CD2EBF38AE0F7B1342@PAUMAILU03.ags.agere.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
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

Williams, Gerald S (Jerry) wrote:
> We're you the one who brought up Unicode earlier? Besides,
> there are numerous situations where files get transferred
> with <CR><LF> without needing to involve Windows, so stray
> <CR> characters occasionally show up here and there. I'm
> sure many of us would like support for <CR><LF> endings on
> Linux as well
---
    Have been on linux for ~7-8 years, unix for 17+ and *nix
utils ~19. The only time I've run into CR-LF issues on *nix,
has been when transporting files to and from the Win or Mac
worlds (MAC using "CR" only).  Maybe linux should ignore "LF"'s
as well to support those coming from MAC's? Then we could
ignore both CRLF and forget this line-oriented stuff and only
work with character streams... ;-)

    Seriously, keeping Linux "LF-only" is useful to filter out
non-portable/non-native DOS files.  It's bad enough Bill G. chose
the "ANSI" literalizing character for a path separator.  Windows (or
DOS) used to support a SWITCHCHAR that fell out use.  Default for
Windows was "/", but if you changed it to "-", you could use "/"
as equivalent to "\" in pathnames.  Too bad they seemed to have
dropped that feature.  Certainly makes POSIX compatibility a bit
more challenging.

    I welcome the change to "LF"-only binary support -- makes CYGWIN
more POSIX- (or linux-) source level compatible.

-lw


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