X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 02A083858031 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1637657701; bh=U7Vo6YdexZjB7NZbpiKufhdn7LO141+A/vct5yUODWY=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=TSxu4aKO8XhTAWQ0xi1S7DSf2ObNUqOO44p5ZiSvUz72CE/Qqr7Dd24P+2jSxKjAR ZrEuEz9ntnHhekrzRdEGga+RIs5bTy+PdET9ASUwM8J7p2hYKftN1j767Z68w+bheX BcbfElVIDy5bKLSw92HlIqkGoHtmtt4puMQfHgjU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2DF363858405 Content-Language: en-US To: "cygwin AT cygwin DOT com" Subject: issues with cygwin programs in windows console Thread-Topic: issues with cygwin programs in windows console Thread-Index: AdfgR3OO3E1W4zeNT++4zfkEj6/YPw== Date: Tue, 23 Nov 2021 08:53:49 +0000 Message-ID: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.120.77.3] x-kse-serverinfo: chr-mail-m07.severstal.severstalgroup.com, 9 x-kse-attachmentfiltering-interceptor-info: protection disabled x-kse-antivirus-interceptor-info: scan successful x-kse-antivirus-info: Clean, bases: 11/23/2021 7:19:00 AM x-kse-bulkmessagesfiltering-scan-result: protection disabled MIME-Version: 1.0 X-KSE-ServerInfo: chr-exch-edg1.severstal.severstalgroup.com, 9 X-KSE-AttachmentFiltering-Interceptor-Info: no applicable attachment filtering rules found X-KSE-BulkMessagesFiltering-Scan-Result: protection disabled X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, HTML_MESSAGE, SPF_HELO_NONE, SPF_SOFTFAIL, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: =?utf-8?b?0JzQuNGA0L7QvdC+0LIg0JvQtdC+0L3QuNC0INCS0LvQsNC00LjQvNC40YA=?= =?utf-8?b?0L7QstC40YcgdmlhIEN5Z3dpbg==?= Reply-To: =?utf-8?B?0JzQuNGA0L7QvdC+0LIg0JvQtdC+0L3QuNC0INCS0LvQsNC00LjQvNC40YA=?= =?utf-8?B?0L7QstC40Yc=?= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" Something, probably a recent windows 10 update (currently at 10.0.17763.2300 - way behind, but it is LTSC) broke cygwin programs using fullscreen (ncurses?) console output e.g. less, mc, vi when run in Windows console windows (cmd and such): they produce no output at all, just black screen with cursor in the top-left corner, but seem to be running and processing keyboard input as expected e.g. when q is pressed less exits and finally prints a screenful of text it was supposed to show from the very start. No issues when these programs run in proper cygwin terminal (mintty). I found two workarounds, but neither one is perfect. One is to set TERM=cygwin but less won't clear the screen on exit and home/end don't work (incidentally setting TERM=xterm like in minnty doesn't help at all). Another workaround is to switch windows console to legacy mode. Is there a better way to run these programs in windows console without starting mintty? -- 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