X-Spam-Check-By: sourceware.org Message-ID: <453D7D8B.9050706@byu.net> Date: Mon, 23 Oct 2006 20:42:19 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: bug bash-3.1.17(9) : CR problems when using cat to generate cmd line arguments References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Howard Mak on 10/23/2006 10:35 AM: >> I can't seem to get the latest version of bash to work with the command >> PROGRAM `cat file_containing_arguments.txt` >> when the file is created on a textmode mount. Seems like carriage returns are not processed correctly. Actually, they are being processed exactly as they would be on Linux. >> >> - I tried using different settings for the shell option igncr, but it didn't seem to help igncr only ignores \r in the input file, not in `` or $() command substitution. But IFS will cover that. Hmm, maybe I should take a closer look at command substitution to see if I can make igncr affect that as well. I'll try and get that in bash-3.2-4. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net volunteer cygwin bash maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFPX2L84KuGfSFAYARAkUYAJ9VraFg07Y8CtvyggU3MVADFBQWwQCaAsyV FrUK3gH2sdomF+Ki4U9NH1A= =PAqU -----END PGP SIGNATURE----- -- 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/