Steve Richmond wrote: > Hi Eric, > > I removed everything and completely re-installed Cygwin with > setup.exe using the UNIX > binary option. I 'set -o igncr' in .bashrc. 'set | grep SHELLOPTS' > show igncr is set. > Yet the problems of bash scripts failing with '\r' errors and the > resultant .CSV has > a '^M' added to each line still appear. So it's going to take more > than just installing > using a binary setup and setting igncr in bash to resolve the > problems. > > I ran D2U on each bash script AND on the data files that it grep-ped > within the > scripts. Voila! Problem solved. Each script and data file came from > a WinME system > that had an aging version of cygwin (circa mid-2005). I wrote a > script to run every > file through d2u. Interestingly that script had to be 'd2u-ed' first. > > So I have a solution but I fail to see why the binary setup and igncr > didn't work. > I don't want to run every file I bring over through d2u as it's > laborious. >
Try running mount and see what that says. I think mountoptions can survive a reinstall. -- Bengt-Arne Fjellner -- 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/