X-Spam-Check-By: sourceware.org Message-ID: <4524F793.9060806@byu.net> Date: Thu, 05 Oct 2006 06:16: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: [ANNOUNCEMENT] Updated: bash-3.1-9 References: In-Reply-To: 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 According to Frank Illenseer on 10/5/2006 1:08 AM: >> Or even experiment with the SHELLOPTS environment variable. If you >> set it >> in windows, even the first run of bash will obey igncr; or, from within >> bash, if you do 'export SHELLOPTS' to convert it from a shell variable to >> an environment variable, then further bash invocations will inherit the >> setting of this option, without having to edit every script. > > This would be a good place for the "igncr" if it worked! > > If i set this variable in windows to the value of just "igncr" I get the > following error upon starting the bash: > > bash: igncr: invalid option name Oh right :( It's a shame that 'set -o' and 'shopt' have different namespaces. It sounds like I should promote igncr to set -o status instead. OK, look for a bash-3.1-10 that does this... - -- 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 iD8DBQFFJPeS84KuGfSFAYARAjRhAKCDKcKu0IpzxoOo93sybi1tMelSSwCfaU23 WI2XU3ZsbS9MestJNFex91A= =Qlfz -----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/