This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
- From: Ken Brown <kbrown at cornell dot edu>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Sat, 21 Sep 2019 22:45:00 +0000
- Subject: Re: Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cornell.edu; dmarc=pass action=none header.from=cornell.edu; dkim=pass header.d=cornell.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VycHzUT2APTL3JjI0gGujL+knP54QiSQGY5U0amUH0o=; b=LwH4fStGwfnXNdVF1f2wWkHUUMErWWqUo4xBbW+QkWFtlOsF6MsMfheCv8a8Yo4y3hWOK5w/PKMYTgA/sqmblwSdfWm534jpdssQOfOtXCQP07OC55RXJO78vjmh5qZBSpb23tDNeyce0dUstxZWlM5dPnubukmvSEOivtUhrlJbmoMo3OEWx0UqsAdlp30HagaqDmRlBCoIngyYfArLY5VfpAwY+dYDmjf/a2v/nRcHSuhIceFJEQCmXJRbks8suUsQ6Ja2l0pGV+tA7ZDk1AoRNQEYv/mh15DICGQbHr1lL2kwR3xlPKpgRfNIVUtaPYpOxrpHOxhbsgxO+m24tw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mxjnwi4XlIEehdSxh9JVmh5/k5edASU96bELtveEYg3/PwhnY6HkSUnA1Hpr/etMlK043E0AQumjvTc/FmtOi11+CPpwm3B93bkaV/MF1e8Oy9zwiqMWAJb8GjJ97MCqyd09GyvgrJ8amnTGnrzFl+UC9SBBMcu+ngoM/KLjmpBiiLIAjMQbey5hCK332jNx3xVR1xkkNoHGmlrk2TNECMclUy2tSBWZzmNLdEQycQK0k89gi+HAg1EnFSzijIY2RbFvfQ3ET3HXAoKRB3vNl/GzX2vy3uKYIpXZLpY/8uTCaRb0Mdx/WF4siTjebXAk4EiLEF9qJGlI1rsrOIMuuQ==
- References: <CADLV35iGHEd1ssLdwMASn9DBnNWudKX-V5CuPiL_5xLtprE3PQ@mail.gmail.com>
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