X-Spam-Check-By: sourceware.org Message-ID: <453F52EA.20205@byu.net> Date: Wed, 25 Oct 2006 06:04:58 -0600 From: Eric Blake Reply-To: cygwin AT cygwin DOT com 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: "Bruun, Peter Michael (HP C&I CME OSS CoE)" , cygwin AT cygwin DOT com Subject: Re: Bash 3.1.17(8): Scripts on textmode mount get problems with CR characters References: <93C4769E3BED6B42B7203BD6F065654C0831DEB0 AT dmoexc01 DOT emea DOT cpqcorp DOT net> In-Reply-To: <93C4769E3BED6B42B7203BD6F065654C0831DEB0@dmoexc01.emea.cpqcorp.net> Content-Type: text/plain; charset=ISO-8859-1 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 http://cygwin.com/acronyms/#PPIOSPE - redirecting to the list. According to Bruun, Peter Michael (HP C&I CME OSS CoE) on 10/25/2006 1:18 AM: > Hello Eric, > > Thanks for the thorough explanation. > > Yes, the missing handling of CRLF in `` and $() is the point of my > message - these should understand the igncr setting. > > Adding d2u is a cludge - I am working in a cross-platform environment > and I do not have d2u on all platforms. I could define it as a dummy > shell-function, but I don't want my Unix scripts to be unnecessarily > polluted by such things. I believe it is an essential part of the > purpose of Cygwin is to hide Windows specific detals, and so having to > pollute my scripts in this way defies the purpose of Cygwin. > > Adding --text to cat is similarly a cludge and would not be portable to > native Unix platforms. > > For now, setting IFS sounds like the best option, but as far as I can > see, it does not affect command substitution either (at the moment of > writing I only have access to bash-3.1-6). > > In some contexts I already do white-space normalization using something > like this: > > F=`echo \`cat f.txt\`` > > With IFS set, this will work, but the method is only correct if f.txt > does not contain significant white-space other than single blank > characters. > > So I am looking forward to bash-3.2-4 with igncr support in command > substitution. When do you think, it will be around? Yesterday evening. > > Best regards, > > Peter Michael Bruun (HP C&I CME OSS CoE) > - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----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 iD8DBQFFP1Lq84KuGfSFAYARAnIhAJ9qUqcC1vCqbmM2WjPkKm6MB+wwwACaA6QJ RyzGNJpf4hZxaAUTFUAtk5A= =La/N -----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/