X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 008AA385BF81
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=towo.net
Authentication-Results:	sourceware.org; spf=none smtp.mailfrom=towo AT towo DOT net
Subject:	Re: Bug with Windows 10 console
To:	cygwin AT cygwin DOT com
References:	<29469422 DOT -1641766844 DOT 1587213736605 DOT JavaMail DOT root AT zimbra76-e14 DOT priv DOT proxad DOT net>
From:	Thomas Wolff <towo AT towo DOT net>
X-Tagtoolbar-Keys:	D20200418160554040
Message-ID:	<1c47ccff-01a5-f4f0-9eed-e7c737a00fb0@towo.net>
Date:	Sat, 18 Apr 2020 16:05:54 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.7.0
MIME-Version:	1.0
In-Reply-To:	<29469422.-1641766844.1587213736605.JavaMail.root@zimbra76-e14.priv.proxad.net>
X-Provags-ID:	V03:K1:6KZE3RWeVA74tliQGk8m01ib/7JNwyK36k+uEM04Kg6Y2xgh87i
	e3tcavaJS6l7ULA6WgAyCBRaRDoDRhnEkzMPY2ng8A11xy6nck2pOTI7KrXsxyDM1s6hidC
	BUgDgXR8e1iHtLajP+YtClhShfwVQ/diECzk7fx5DwPEjMFqvwBISoG+7CIYw8INg16+eAB
	73BYGCeLCyn8CQvwuTwMg==
X-UI-Out-Filterresults:	notjunk:1;V03:K0:Ih1nYWs2IX4=:Tx4Er0aJk88/4dkre50El3
	fIYbBjlhJfW7Bwpp2j8uhUfYESm9P+tR0L6pAO8BWGeaYt9/+eI6ADvVIe+VwBV1i+pJv3RvI
	JdawveLxRUIiOJW7MBTkGRguc+1IR0hw5jZC6farYr9/42CRurRHYO+tN+C2tViNKdyyZ6B/H
	6fUrA6ZTMd+QdUhgB5LKCkUyVIImJmmlqEyMSyFx4PTK6sYZSYmECusmWj3ejhI//rvhcNlZo
	Mlo41WjQmg53QIVDK+oxMJiJRfCibxK337nqx0q+KdWCb6b1uldzl7H5P3nN6lwaQC9pL9NXk
	st4+98ib/ktofA+jZjlJbSDUNgpBqFoS30ZdddQCDru6LZCNkgeXoY7A21rkjJV2XEcUJ+STx
	O56vmn7niLr1FqpdWSvE0aXFBMJILKPg/gsxTa3VEfD4EUC9sjGm9eEGK9TW3bm/IKseT0a52
	egUif1hlif/Gdq03pJx9TvuppqTqDaVEH4f3ErLVlFd51dhNpgvTBtAm6mRakdmoiLc+PBVeK
	zhGmAvIkPW2Haa2mDyr3mcWhwPpCHX89cw2Fjaa20ZvJ6dOTYCbKyQ8VLUOKLt/MYDfclRTdO
	dhXVtDV1cSEu49ULBdKeMV6b6mvSUmiWVy/sErKs1vBh+O7w/iPw3yRTPR8IkS1BDMTosf6OB
	0+wQ/BDDISKsedthXQaX1GSHAo/TlwY2WNDayTEpls4Km4CrgqA7zKysCVpc1L17MCwGQws1I
	YA2RxalhU6epDsmxaIarU51mFkkeiQmToxE8yIIdSYDapFzacCAm1VIyIZqanxKUqdMUZpgPk
	GUGGkvQ/KUsV73+uktOES7UoPVm2pl+LND9ulxEgSaBFwZO1VM=
X-Spam-Status:	No, score=-11.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,
	SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 03IE6Tcv013297

Am 18.04.2020 um 14:42 schrieb akiki AT free DOT fr:
> Hi,
Bonjour
> To day, all programs are upgraded permanently. A good and a bad thing.
> Windows 10, cygwin ...
> One recent upgrade, I don't target exactly which one, has broken my environment.
>
>
> Current versions as reported by cygcheck :
>   Windows 10 Professional Ver 10.0 Build 18363
>   cygwin 3.1.4-1 OK
>   bash 4.4.12-3 OK
>
> I am using 2 kinds of console to interact with cygwin
>   mintty : using pty as TTY
>   bash under cmd : using cons as TTY
>
> These two were working correctly until recently, but now only mintty stay correct.
>    -- in reality it's seems
> The principal difference is about Ctrl-C interaction.
> With the 2nd kind of TTY, a same program using curses, on Ctrl-c
>   interrupt the program
>   give me a prompt
>   but the terminal stay in curses mode, ie without echo and bad new line
> I have to do "reset" (/bin/reset) to restore the terminal
>
> So the interrupt handling has changed.
> Who is responsible.
It might help if you tell us *which* program behaves like that.
>
> I had a look about the new Window Console Legacy.
> With this new console, we saw a black screen with color bash prompt.
>   
> So with bash, is it possible to work with one or other TTY mode ?
>
> Howto understand this problem and what can I do to correct it.
> mintty present some problems with my environment and because of that I use the second form of TTY.
Which problems?

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -