-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Jim Easton on 11/8/2006 7:47 PM: > Interesting: When I do that it works fine in both cases, even when I > force a <CR> at the end of the line. It appears as though when bash > sees the <CR> at the end of line it automatically deletes it. Mind > you I am using an earlier version of cygwin; > > CYGWIN_NT-5.1 1.5.19(0.150/4/2) 2006-01-20 13:28 > and so presumably an earlier version of bash > GNU bash, version 3.00.16(14)-release (i686-pc-cygwin)
Consider upgrading - we're at cygwin 1.5.21 and bash 3.1 (or experimentally, 3.2). This list does not make it a habit to support older than the previous release, because of the bugs that have been fixed since. > > Is there a bash variable that controls such behaviour (I can't find one) > or was there an upgrade in the interim? HAVE YOU NOT BEEN READING THE ARCHIVES? This has been the hottest topic on this list _all month long_. http://cygwin.com/ml/cygwin-announce/2006-11/msg00009.html - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----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 iD8DBQFFUp6f84KuGfSFAYARApo5AKCr1yKTkgQh/AkfyFOe59EKHN3s7ACdGM/e dRx+ozswfxVbNY7J6oxPNIs= =nBor -----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/
