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=WQRQXrJw+3XioyM2
	4UsbRlVrG00MSFN3z/qXq5gzxhY7XGiKbB6Las4z5dRSDbIiItjauZ+n5ePv5XQH
	oOyG83F8YD0sTyUwiZsCt3jZjp+oOitnu/e7aTvGPcZ+fxyklB4ht7YYS1wuxspZ
	XURu+SWIKE/AkN8ohCy0qf9qQSM=
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=8n3NXT3zJJfKapPcd7USyn
	Awqx0=; b=b0GowfKg32KYBDx8M+P8kldhksJZAGZLubJEXpxrg+rO8K34grmD21
	vdAvnw5RqZxM/dpRq6RDPH1DgME1OoKZYgZSm0SZAfHW003EL14wmnmSos+h1GJp
	XPXbK8n06xR5d5YEMQGMQEs3Co1qCxqpAqicYzBrbCU2yh7cy+s1E=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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, ancient, msk, MSK
X-HELO:	forward3p.cmail.yandex.net
Authentication-Results:	smtp2j.mail.yandex.net; dkim=pass header.i=@yandex.ru
X-Yandex-Suid-Status:	1 0,1 0
Date:	Tue, 30 Aug 2016 06:14:15 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<181446230.20160830061415@yandex.ru>
To:	Eric Blake <eblake AT redhat DOT com>, cygwin AT cygwin DOT com
Subject:	Re: bash: igncr shell option breaks my PS1 prompt
In-Reply-To:	<8980687a-967e-88d8-2a94-f485731fafe9@redhat.com>
References:	<CAPTiy3PE0gZ-hpvQbxVkfaZfxtppDx7RG85WtuigpnL54WZbDA AT mail DOT gmail DOT com> <CAPTiy3N-n5krtWcZuK8-pBQE_efzroS6rizknHqU2tE+BYaMQQ AT mail DOT gmail DOT com> <8980687a-967e-88d8-2a94-f485731fafe9 AT redhat DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Eric Blake!

> But it seems like \n handling in PS1 is independent of any change in
> handing in the 'read' builtin.  As evidence, I ran the following test
> using the older bash-4.3.42-4 build:

> $ bash-4.3.42-4
> $ set -o igncr
> $ PS1='$(date)\n# '
> bash: command substitution: line 1: syntax error near unexpected token ')'
> bash: command substitution: line 1: `date)'

That's interesting.

I've just tried it on Linux.

$ PS1='$(date)\n\$ '
Tue Aug 30 06:10:48 MSK 2016
$ bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)

(No idea why they ship this ancient version...)
And on Cygwin

$ PS1='$(date)\n\$ '
Tue Aug 30 06:12:38 MSK 2016
$ bash --version
GNU bash, version 4.3.46(6)-release (x86_64-unknown-cygwin)
$ set -o igncr
-bash: command substitution: line 1: syntax error near unexpected token `)'
-bash: command substitution: line 1: `date)'

> $ exit

> So you have uncovered a latent problem, unrelated to the recent igncr
> fixes, but which is indeed tied to the overall igncr patches, and which
> you had no reason to trip over until the igncr change to 'read' changed
> your desire to use igncr.

Seems like it is related, at least in some way.


-- 
With best regards,
Andrey Repin
Tuesday, August 30, 2016 06:09:31

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

- Raw text -