This is the mail archive of the
mailing list for the Cygwin project.
Re: trouble with bash / if in recent release / update ?
-----BEGIN PGP SIGNED MESSAGE-----
According to Daniel Brockman on 1/30/2007 12:18 AM:
> A blank line in the script file produces err msg
> : command not found
> I can't figure out a way to make the new version of sh.exe work. Imho, it's
> I found this in the archive...
> 4a. For a single affected script, add this line just after the she-bang:
> (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
You were correct - it is not sh that is broken, it was your scripts. And
have you considered point 2, that running d2u might be easier than using
> The value of the latest enhancement isn't immediately apparent to me.
READ THE ARCHIVES! This topic has been talked to death in the past two
months. The value is the fact that Cygwin on binary mount points is
_designed_ to emulate Linux, and on Linux, you will get the _same_ syntax
errors with raw carriage returns in your scripts; furthermore, this change
was made in response to a performance bug. In my opinion, text mode files
are a hack for people unable to follow Linux semantics; either use text
mount points, or specifically ask bash to operate in text mode; either
way, it should help make it clear to yourself that you are moving away
from Linux behavior and getting slower performance as a result.
Don't work too hard, make some time for fun as well!
Eric Blake email@example.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html