From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101416 invoked by alias); 27 Aug 2016 16:20:16 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 101300 invoked by uid 89); 27 Aug 2016 16:20:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.0 required=5.0 tests=BAYES_50,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=H*F:D*yandex.ru, yandexru, UD:yandex.ru, yandex.ru X-HELO: forward4j.cmail.yandex.net Received: from forward4j.cmail.yandex.net (HELO forward4j.cmail.yandex.net) (5.255.227.22) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 27 Aug 2016 16:20:05 +0000 Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [95.108.131.191]) by forward4j.cmail.yandex.net (Yandex) with ESMTP id C5695207FA; Sat, 27 Aug 2016 19:20:02 +0300 (MSK) Received: from smtp2j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2j.mail.yandex.net (Yandex) with ESMTP id 02CE61060C89; Sat, 27 Aug 2016 19:20:01 +0300 (MSK) Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id YLj3OCDRdS-K1WmUsgD; Sat, 27 Aug 2016 19:20:01 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Sat, 27 Aug 2016 16:15:01 -0000 Date: Sat, 27 Aug 2016 17:24:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <1635303092.20160827191501@yandex.ru> To: Gene Pavlovsky , cygwin@cygwin.com Subject: Re: Script broken after updating bash to 4.3.46-7? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-08/txt/msg00554.txt.bz2 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