X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Daniel Brockman Subject: Re: trouble with bash / if in recent release / update ? Date: Tue, 30 Jan 2007 07:18:12 +0000 (UTC) Lines: 30 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Tim Hanson faz.de> writes: > [...] > i'd be grateful for pointers. (or advice on how to provide more clues.) > > cheers, > > Tim > > I found this in the archive... From: Eric Blake byu.net> Subject: [ANNOUNCEMENT] Updated: bash-3.2.9-11 Newsgroups: gmane.os.cygwin Date: 2007-01-27 16:30:22 GMT (2 days, 14 hours and 41 minutes ago) [...] 4a. For a single affected script, add this line just after the she-bang: (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed 4b. For a single script, invoke bash explicitly with the shopt, as in 'bash -o igncr ./myscript' rather than the simpler './myscript'. [...] The value of the latest enhancement isn't immediately apparent to me. db -- 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/