X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=UkhgVG/7pUCZYPtPGTg3N4nItL28j/VU7BZqK7DZor8
	677ehEzWNM/J009X3cMdxKuUimIiSJ2rSlY/eer8AiCOxOGTsTr51fuzgGoOCdq9
	P5T08TffowOcVP0g60dSqLlRYrvOrT4lNmVwer3Uhqh+geoMeOVBNsbQsr/AdWtk
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 s=default; bh=tk2PdTAIePT/67OOcLDp0XLZpDU=; b=AiYz0xxqDDFfxqcSE
	U3PSax+jyF2Pny0KQ/zt7+AGZlGr0tqtlV5F/iOI/k24XYk81kShQqFBVryoVsK/
	0tQp7fPoqOew//ZzvLauGsufNRFZbRS9u5gInIRe8zQ+wsu22TjGBjxx+sgEZsMN
	CAPhw7zxxhNvfO74gAaXCMjn/o=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-5.7 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 spammy=HX-Languages-Length:823, H*F:D*ne.jp
X-HELO: conssluserg-03.nifty.com
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com x7MAggN6019038
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp;	s=dec2015msa; t=1566470562;	bh=ehhPx9JCaxFZJkyYnLLBxRmtoPYn5sZ/w28RvXchNC4=;	h=Date:From:To:Subject:In-Reply-To:References:From;	b=pNPFBQsod++bnnED8c9vBdGeBN7Pqqb055SjMZ3Wm+zNQmjTxWNkQAAKAU7I8PaTx	 romYkHtgFWsfnTbtoSp7/uGhiGGJG85vyYvBYTtkOUc/VcfOr18AiceJ/yZ/NU47jH	 FPA40ezR6kTD+dcnAR6c0xpfmhop0KUTTZ1HSERkSfvo+NZupUpL3zuqoIBlcieIjp	 TDGppA7dGLuQIUF8ciP44Z6tdZuH4d1+prQSpvm7uljI+ftY2PGCh5Usigkr0q6e3N	 0BC8BfN4EuUkTV+O/owpTNE5qwoX+RgSlaxbxu63bB91+YXghMiVYtI/No2fl/2cA+	 Rb19YERbdBNNQ==
Date: Thu, 22 Aug 2019 19:42:51 +0900
From: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To: cygwin AT cygwin DOT com
Subject: Re: TEST: Cygwin 3.1.0-0.2
Message-Id: <20190822194251.d7c6de37c15e9a716e3d1ee3@nifty.ne.jp>
In-Reply-To: <5D5DA13A.4040904@tlinx.org>
References: <announce DOT 20190819103956 DOT GK11632 AT calimero DOT vinschen DOT de>	<5D5DA13A DOT 4040904 AT tlinx DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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 DOT yano AT nifty DOT ne DOT 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