RE: bash CRLF problems (I have read the recent announcement)

Kevin Layer wrote: > I'm really perplexed by the following behavior: > > [EMAIL PROTECTED] ~ > $ cat -v foo1.sh > echo 8010 > foo1.out > > [EMAIL PROTECTED] ~ > $ cat -v foo2.sh > sh foo1.sh > version=`cat foo1.out` > echo ${version}.bar > foo2.out > cat -v foo2.out > > [EMAIL PROTECTED] ~ > $ sh f

RE: bash CR and backquotes trouble

Nicolas Roche wrote: > t=`gcc --print-multi-lib` where gcc is a mingw gcc. > > As my gcc is a mingw program, it outputs CR/LFs. In previous versions > bash used to ignore the CR, so t variable was not containing any CR. > Now this is no more the case and this is causing some troubles Looking back

RE: Similar Bash 3.1.18 CR/LF Problem

Eric Blake wrote: > But I'm not sure whether making > igncr the default in 'bash --posix', aka '/bin/sh', is wise, since POSIX > does not permit this behavior. My only concern is that by making igncr > cognizant of whether posix behavior is requested, people will start asking > 'why does my script

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

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: Similar Bash 3.1.18 CR/LF Problem

> > I really am getting a bad feeling that, rather than FIXING THE SCRIPTS, > everyone is reverting to using text mode mounts which are not what we > generally recommend. > > cgf > As much as I would love to work in a pure cygwin environment it's not always possible. In our particular case the

RE: Similar Bash 3.1.18 CR/LF Problem

> > > > IIRC, Cygwin explicitly treats out-of-mount (Win32) paths as binary. > > Igor > > > Yes, that's fits my recollection as well. Since both of us recall this, > there's no need for anyone to check the source. Two IIRCs means we must > be right! ;-) > > :) That's how my rulebook work

RE: Similar Bash 3.1.18 CR/LF Problem

> > Apologies that this is being written the day after without real output. > > I'm now at my desk without easy access to the machine in question. > > But... > > > > We've been using Cygwin with text-mode mounts for a long time without > > any problems. A new engineer started the other day, instal

Similar Bash 3.1.18 CR/LF Problem

Apologies that this is being written the day after without real output. I'm now at my desk without easy access to the machine in question. But... We've been using Cygwin with text-mode mounts for a long time without any problems. A new engineer started the other day, installed a brand-spanking-ne