X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 66D693857C4B
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1637660243;
	bh=1yPiNXi1JdBIHRZzJaX0YyHL7bXYnuEey9ogdkB6258=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=Rw1X+jTjk+rSIEtbU2K8HXFZHk5ZCFdLfqNe2dh8Hyr1h0+ppBlf90x5XdURerUhk
	8lkAjtRZdh4/J8tNJSvFUrShzbm4fOmFZJVx+aZI7BdBeJNJkZgYI9vOhJP+KD54xp
	XwdgJIrGUKY3u5+wzFr5BaVR5KWitGCZArGS3XDY=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 8FFAE3858D28
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 1AN9ZMUa007994
X-Nifty-SrcIP:	[110.4.221.123]
Date:	Tue, 23 Nov 2021 18:35:23 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: issues with cygwin programs in windows console
Message-Id:	<20211123183523.e0db4d1f5f1f00b600c76f89@nifty.ne.jp>
In-Reply-To:	<b5035ca1a7b5408a85f600794356f013@severstal.com>
References:	<b5035ca1a7b5408a85f600794356f013 AT severstal DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-6.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) 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:	<https://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:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Tue, 23 Nov 2021 08:53:49 +0000
$B'.'Z'b'`'_'`'S(B $B'-'V'`'_'Z'U(B $B'#']'Q'U'Z'^'Z'b'`'S'Z'i(B via Cygwin <cygwin AT cygwin DOT com> wrote:

> 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?

I cannot reproduce your problem.

Please provide
cygcheck -s -v -r
result.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
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 -