X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Bash and CR/LF line-endings
Date: Wed, 4 Oct 2006 09:57:35 -0400
Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F7B1342@PAUMAILU03.ags.agere.com>
In-Reply-To: <000201c6e75c$97a8afe0$020aa8c0@DFW5RB41>
From: "Williams, Gerald S \(Jerry\)" <gsw@agere.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k94DvuXe027468

Gary R. Van Sickle wrote:
> At the risk of being over-obvious, Linux users... use Linux. In such
> an insular environment, perhaps they have the luxury of only using
> the One True Text File Format (whatever that is).

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.

gsw

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