Greetings, Gene Pavlovsky! > Looks like it's related to a recent change in bash, which is `read` > now honors Cygwin-specific `igncr` shell option (`set -o igncr`), > which I didn't enable. > Adding `set -o igncr` to the top of the script does the job, however > I'd like to know how many more scripts are potentially malfunctioning > now? > It's lucky that one sent e-mails on errors, some others might just > break silently. > Is it advisable to add `set -o igncr` to /etc/profile or SHELLOPTS? I > didn't use that feature before and am worried about some other > negative side effects.
It is advisable to not have CR's in your scripts to begin with. -- With best regards, Andrey Repin Saturday, August 27, 2016 19:14:10 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
