DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=cQFclSwWbc9PTMZodarnI7k2a0ycA
	GtkYGmPzcM21S+g78NEgIuNZlpaFER0ylk2EXqKXnzGEVEmDNZQm4mVDUmq7BjNU
	EcgEL+gNkbtZFLE4TrjJlDrG9TupTCbOZ+FpAji1w08FbegE7BGheZfMrl1ymR1d
	wifeLmCAqHPMQc=
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
MIME-Version: 1.0
From: connor horman <chorman64 AT gmail DOT com>
Date: Sat, 21 Sep 2019 12:06:49 -0400
Message-ID: <CADLV35iGHEd1ssLdwMASn9DBnNWudKX-V5CuPiL_5xLtprE3PQ@mail.gmail.com>
Subject: Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

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.

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