X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 22 Feb 2008 14:14:58 -0500
From: Doug McIlroy <doug AT cs DOT dartmouth DOT edu>
Message-Id: <200802221914.m1MJEwJB019090@tecumseh.cs.dartmouth.edu>
To: cygwin AT cygwin DOT com
Subject: bash bobbles CR-LF
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Most cygwin utilities gracefully handle text files with lines
terminated by either a bare newline or carriage return-linefeed.
Not so with bash (version 3.2.33(18)-release (i686-pc-cygwin)).
There are various symptoms, but the clearest is that, in
a script with CR-LF terminations, an empty line draws the
diagnostic, "$'\r': command not found".

Doug McIlroy

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