* Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
@ 2019-09-21 17:41 connor horman
2019-09-21 21:02 ` Eliot Moss
2019-09-22 6:06 ` Ken Brown
0 siblings, 2 replies; 3+ messages in thread
From: connor horman @ 2019-09-21 17:41 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
2019-09-21 17:41 Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal connor horman
@ 2019-09-21 21:02 ` Eliot Moss
2019-09-22 6:06 ` Ken Brown
1 sibling, 0 replies; 3+ messages in thread
From: Eliot Moss @ 2019-09-21 21:02 UTC (permalink / raw)
To: cygwin
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.
Others are certainly more knowledgeable on this than I am, but since
colors and such work fine through cygwin on an xterm, I think it has
to do with the terminal, not that cygwin per se (i.e., not the dll).
Regards - Eliot Moss
--
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal
2019-09-21 17:41 Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal connor horman
2019-09-21 21:02 ` Eliot Moss
@ 2019-09-22 6:06 ` Ken Brown
1 sibling, 0 replies; 3+ messages in thread
From: Ken Brown @ 2019-09-22 6:06 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-21 22:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-21 17:41 Cygwin 3.0.7 on Windows 10: ANSI Escape Sequences not affecting color when run in Windows Terminal connor horman
2019-09-21 21:02 ` Eliot Moss
2019-09-22 6:06 ` Ken Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).