DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=yo+g9UfD7ODpWv+kcOCTwBzzFRWsuO25vZ/B6Pi5kqm
	/sbem714IXV8Q3oeinmDD6rhrsdpQJ4AHd1HgLpflc0BUYDEfOubUj7iZecw1U1+
	QhWnCrPFpZWD2v3y6saA4b9o6EhIEC8AgA3lhAFT8uPgjLC1qSQ68p31RJTmP8PY
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5D5DA13A.4040904@tlinx.org>
Date: Wed, 21 Aug 2019 12:53:30 -0700
From: L A Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: TEST: Cygwin 3.1.0-0.2
References: <announce.20190819103956.GK11632@calimero.vinschen.de>
In-Reply-To: <announce.20190819103956.GK11632@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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?

tnx for the new stuff!
-linda


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