Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-05 Thread Eric Blake
-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 conv

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-05 Thread Frank Illenseer
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 setti

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-04 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to David Picton on 10/4/2006 10:13 AM: >> (shopt -s igncr) 2>/dev/null && eval 'shopt -s igncr';# > > Alternatively, you can set the environment variable BASH_ENV to the name > of a > file containing startup commands for all bash scripts. I

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-04 Thread David Picton
From: Eric Blake To: cygwin at cygwin dot com Date: Mon, 02 Oct 2006 21:51:04 -0600 Subject: [ANNOUNCEMENT] Updated: bash-3.1-9 Reply-to: cygwin at cygwin dot com Reply-to: The Cygwin Mailing List -BEGIN PGP S

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-04 Thread Ken Wagnitz
Wilks, Dan intuit.com> writes: > > Eric, as one of the complainers :) thanks. I just wanted to check in > and > say that our case of executing a cr/lf script via a DOS path on a text > mount > is working as well as it used to. > > I echo that sentiment. Now I don't feel so "left behind". :)

RE: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-03 Thread Wilks, Dan
Eric Blake wrote: > First, if a script is > specified with a DOS path instead of a POSIX path (although this is not > the recommended behavior in cygwin), bash will ensure that the underlying > mount mode is respected, rather than the default cygwin behavior of using > binary mode, allowing the us

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-03 Thread Cary Jamison
I also appreciate the work you are doing, Eric. But, (ooh, one of those dreaded buts!), I predict this will be a source of endless trouble, still. Like CGF said earlier, you want to encourage people to use binary mounts, yet their \r\n scripts are not going to work unless they run on a text-mo

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-03 Thread mwoehlke
Christopher Faylor wrote: On Tue, Oct 03, 2006 at 04:28:13PM +, Eric Blake wrote: mwoehlke writes: Eric Blake wrote: Second, this release adds a new shopt, igncr, which dynamically tells bash to ignore all \r in the input file when it is set; however, it defaults to unset. So, I keep wanti

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-03 Thread Christopher Faylor
On Tue, Oct 03, 2006 at 04:28:13PM +, Eric Blake wrote: >mwoehlke tibco.com> writes: >> Eric Blake wrote: >> > Second, this release adds a new shopt, igncr, which dynamically >> > tells bash to ignore all \r in the input file when it is set; however, it >> > defaults to unset. >> >> So, I kee

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-03 Thread Eric Blake
mwoehlke tibco.com> writes: > > Eric Blake wrote: > > Second, this release adds a new shopt, igncr, which dynamically > > tells bash to ignore all \r in the input file when it is set; however, it > > defaults to unset. > > So, I keep wanting to know if you are thinking about submitting this >

Re: [ANNOUNCEMENT] Updated: bash-3.1-9

2006-10-03 Thread mwoehlke
Eric Blake wrote: Second, this release adds a new shopt, igncr, which dynamically tells bash to ignore all \r in the input file when it is set; however, it defaults to unset. So, I keep wanting to know if you are thinking about submitting this upstream (or have you done so already?)... -- Ma