From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: issues with cygwin programs in windows console
Date: Tue, 23 Nov 2021 18:35:23 +0900 [thread overview]
Message-ID: <20211123183523.e0db4d1f5f1f00b600c76f89@nifty.ne.jp> (raw)
In-Reply-To: <b5035ca1a7b5408a85f600794356f013@severstal.com>
On Tue, 23 Nov 2021 08:53:49 +0000
Миронов Леонид Владимирович via Cygwin <cygwin@cygwin.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.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-11-23 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 8:53 Миронов Леонид Владимирович
2021-11-23 9:35 ` Takashi Yano [this message]
2021-11-26 20:08 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211123183523.e0db4d1f5f1f00b600c76f89@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).