DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; q=dns; s=default; b=fqlyHILBbCH74FTuToyj5nBpZ8u5I
	m/slo7sdoHDebhQ9I1fFmZMDQaKqsK0bIy2EGmIPrVN4ALj6Fyd6515s4S0x9XMr
	e98P5I5As6SeU84uW+nCj4fHpfAdRyPaAHnAUaF3VAtYz/FXzDrkHhl4FggeyVkL
	gx8ETYX6TQF1MU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Ken Brown <kbrown AT cornell DOT edu>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
Date: Sat, 21 Sep 2019 22:45:00 +0000
Message-ID: <a43f6dc8-4135-8433-71b0-82b44ce0c915@cornell.edu>
References: <CADLV35iGHEd1ssLdwMASn9DBnNWudKX-V5CuPiL_5xLtprE3PQ AT mail DOT gmail DOT com>
In-Reply-To: <CADLV35iGHEd1ssLdwMASn9DBnNWudKX-V5CuPiL_5xLtprE3PQ@mail.gmail.com>
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
received-spf: None (protection.outlook.com: cornell.edu does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <D2D8324B092F224A897CE39AFD2E0CD4 AT namprd04 DOT prod DOT outlook DOT com>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-userprincipalname: cvFOGEsRgr5Ipf2d3JNW6doK3CyAWBGlPLh1W0Agb3inba1rqC7mT484xSUMIvhUdTGZjvobxavT1slJw2N3rQ==
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x8LMkGc6027829

On 9/21/2019 12:06 PM, connor horman wrote:
> When using windows terminal, programs using the C Functions provided
> by cygwin1.dll to print to stdout (such as printf, puts), do not
> render the text color as would be appropriate when using an ANSI
> Escape sequence, such as "\033[38;2;255;0;0m". The functionality has
> been confirmed on native linux with glibc, as well as when displaying
> to mintty.exe. Additionally, the issue does not occur with native
> windows executables performing the same task, linked with msvcrt as
> the C library implementation, both run through windows command line
> programs such as cmd.exe and powershell, and cygwin bash. The issue
> seems to be a disparity between the handling of these escape sequences
> in cygwin1.dll and in Windows Terminal as is noted in the issue filed
> at https://github.com/microsoft/terminal/issues/2837.

By "using windows terminal", do you mean the terminal you get by running 
Cygwin.bat?  If so, the issue has been fixed for the upcoming release of 
cygwin-3.1.0.  You can test it by using Cygwin's setup to install the test 
release cygwin-3.1.0-0.5.

Ken

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