X-Spam-Check-By: sourceware.org
Message-ID: <2fc802c00610311212i7bcc6b06sca14c0fda6ac6346@mail.gmail.com>
Date: Tue, 31 Oct 2006 20:12:02 +0000
From: "David Picton" <djpicton AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Bash 3.1.9 and 3.2.4: igncr setting not effective for 'source'd files
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

Unfortunately I have to report that both versions of bash don't
implement the igncr setting if
commands are read from a sourced file.

For example, I have /etc/profile set up to issue

shopt -s igncr #

as the first line (or

set -o igncr; export SHELLOPTS #

for version 3.2.4)

If I do

unix2dos /etc/profile

the command

source /etc/profile

produces a series of error messages, indicating that <cr> characters
are not being
ignored.

If I issue the file as a script,  e.g.
bash /etc/profile

there are no errors.

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