On 10/05/2011 02:37 PM, Russ Browne wrote: > Configuration Information [Automatically generated, do not change]: > > Machine: i686 > > OS: cygwin > > Compiler: gcc-4 > > Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' > -DCONF_OSTYPE='cygwin'
Given that you are trying to use cygwin, this may be a question better asked on the cygwin lists. > I thought this must surely be a simple goof that would be fixed > in the > > next release, but when I reloaded cygwin for my new PC late last > year > > the bug was still there. This is not a bug, but a conscious design decision. In particular, the cygwin port of bash intentionally behaves like Unix in treating CR as literal characters (for speed and POSIX compliance reasons) unless you take explicit measures to request that it ignore CR (your explicit request is what allows bash to ignore POSIX). Read the cygwin bash release notes for more details on the measures you can take: http://sourceware.org/ml/cygwin-announce/2011-02/msg00027.html -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
