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 4D372385B835 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=free.fr Authentication-Results: sourceware.org; spf=none smtp.mailfrom=akiki AT free DOT fr Date: Sat, 18 Apr 2020 14:42:16 +0200 (CEST) From: akiki AT free DOT fr To: cygwin Message-ID: <29469422.-1641766844.1587213736605.JavaMail.root@zimbra76-e14.priv.proxad.net> In-Reply-To: <535856733.-1642430415.1587202868364.JavaMail.root@zimbra76-e14.priv.proxad.net> Subject: Bug with Windows 10 console MIME-Version: 1.0 X-Originating-IP: [2a01:e0a:d:48f0:95a:bad:7bf5:b1e2] X-Mailer: Zimbra 7.2.0-GA2598 (ZimbraWebClient - GC81 (Win)/7.2.0-GA2598) X-Authenticated-User: akiki AT free DOT fr X-Spam-Status: No, score=1.8 required=5.0 tests=BAYES_50, FREEMAIL_FROM, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Level: * 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 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 03ICgkdv005408 Hi, 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. 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. Sorry for my bad English. -- 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