From: Andrey Repin <anrdaemon@yandex.ru>
To: Gene Pavlovsky <gene.pavlovsky@gmail.com>, cygwin@cygwin.com
Subject: Re: Script broken after updating bash to 4.3.46-7?
Date: Sat, 27 Aug 2016 17:24:00 -0000 [thread overview]
Message-ID: <1635303092.20160827191501@yandex.ru> (raw)
In-Reply-To: <CAPTiy3PXKi+8c+7VGOe+KMjqKmHAYfLERtsLcYKsz-5=C6nUaA@mail.gmail.com>
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
next prev parent reply other threads:[~2016-08-27 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 10:28 Gene Pavlovsky
2016-08-27 11:25 ` Gene Pavlovsky
2016-08-27 17:24 ` Andrey Repin [this message]
2016-08-28 10:19 ` Gene Pavlovsky
2016-08-29 13:28 ` Nellis, Kenneth
2016-08-29 14:05 ` cyg Simple
2016-08-30 3:21 ` Eric Blake
2016-08-30 18:21 ` cyg Simple
2016-08-30 18:32 ` Eric Blake
2016-08-31 10:16 ` cyg Simple
2016-09-04 9:38 ` Gene Pavlovsky
2016-09-04 17:37 ` Lee
2016-09-05 23:37 ` Gene Pavlovsky
2016-09-06 13:15 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1635303092.20160827191501@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=gene.pavlovsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).