X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; q=dns; s=default; b=RkiducemFxJUvyhv LbpY9bPiZ2Pd84WrqtI6HknOu8Gn5UU6ecEIoMuK7Dv3TGcMz/cOJHnMFB6LXaXk 6i5jwlfrGziZpVX8FARNy87NwzLUG/F+xEIBnbgnahQyOiC3PkK0gkVyS+rt3QuP xBSIUwPGwR9BnNxbz9gi4HrDXwE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=default; bh=qw0SaAHfKXZiONqUMjnNmt 6pVxU=; b=vOuFF/JmjGzRrD8Htxyx7SoCJVtfO+qzvFtSntWhplVeC+paXcVzIn dTng0yjAXKF8znx+wB07P1SwdFOIFMaYgdkv4oOCvpwr2M5HjaYrN4wKSOOH0gDX nmIEVVLIA5CUHvSfdJHvDr4pyxzuMRhPP/ZHPD2pOQ6zeqE0fLgbg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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 Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Date: Sat, 27 Aug 2016 19:15:01 +0300 From: Andrey Repin Reply-To: cygwin AT cygwin DOT com Message-ID: <1635303092.20160827191501@yandex.ru> To: Gene Pavlovsky , cygwin AT cygwin DOT 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 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