public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.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 21:02:00 -0000	[thread overview]
Message-ID: <4c562448-e458-4ae5-14ce-493a38ae3bf3@cs.umass.edu> (raw)
In-Reply-To: <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.

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

  reply	other threads:[~2019-09-21 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21 17:41 connor horman
2019-09-21 21:02 ` Eliot Moss [this message]
2019-09-22  6:06 ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4c562448-e458-4ae5-14ce-493a38ae3bf3@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).