Script broken after updating bash to 4.3.46-7?
Sun Aug 28 10:19:00 GMT 2016
That's what I personally think, none of the scripts I use have CRs,
and this is why I'd prefer not using the `igncr` option.
However the recent change to how `read` works makes it necessary to
modify existing scripts which interoperate with Windows console
programs (in my case, Windows build of mysql (MariaDB)) that produce
CRLF line endings.
On 27 August 2016 at 19:15, Andrey Repin <firstname.lastname@example.org> wrote:
> 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
>> 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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin