From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: TEST: Cygwin 3.1.0-0.2
Date: Thu, 22 Aug 2019 11:46:00 -0000 [thread overview]
Message-ID: <20190822194251.d7c6de37c15e9a716e3d1ee3@nifty.ne.jp> (raw)
In-Reply-To: <5D5DA13A.4040904@tlinx.org>
On Wed, 21 Aug 2019 12:53:30 -0700
L A Walsh wrote:
> On 2019/08/19 03:39, Corinna Vinschen wrote:
> > - Add 24 bit color support using xterm compatibility mode in Windows 10
> > 1703 or later. Add fake 24 bit color support for legacy console,
> > which uses the nearest color from 16 system colors.
> >
> ??? Why would xterm need Win10 for 24bit color? I'm slightly confused --
> is it only the non-X version that had this limitation?
To tell the truth, git log says:
commit bd627864ab4189984cdb0892c00f91e39c4e8243
Cygwin: console: support 24 bit color
This feature is for console, that is, command prompt.
Command prompt in Win10 1703 has xterm compatible mode,
which is enabled by passing ENABLE_VIRTUAL_TERMINAL_PROCESSING
to SetConsoleMode().
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-08-22 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 11:20 [ANNOUNCEMENT] " Corinna Vinschen
2019-08-19 14:01 ` Takashi Yano
2019-08-19 14:03 ` Corinna Vinschen
2019-08-19 15:20 ` Takashi Yano
2019-08-19 16:50 ` Corinna Vinschen
2019-08-21 22:21 ` L A Walsh
2019-08-22 11:46 ` Takashi Yano [this message]
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=20190822194251.d7c6de37c15e9a716e3d1ee3@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).