Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ANSI Invert displays incorrect colours #6671

Closed
Starwort opened this issue Jun 25, 2020 · 4 comments
Closed

ANSI Invert displays incorrect colours #6671

Starwort opened this issue Jun 25, 2020 · 4 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Starwort
Copy link

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Microsoft Windows [Version 10.0.18362.900]
Windows Terminal version (if applicable): 1.0.1401.0

Any other software? None relevant

Steps to reproduce

Set your foreground and white colours, (as well as background and black colours) to something you will be able to distinguish.
For the purpose of this example, foreground is green, background is dark (#121212 for Terminal and #0c0c0c for WSL TTY), white (terminal) is red, and black (terminal) is blue
Launch e.g. Python (anything that can print ANSI codes), print ANSI invert and restore codes as follows:

>>> print('\x1b[7m')
>>> print('\x1b[27m')

Expected behaviour

Output similar to in the WSL dedicated terminal:
image

Actual behaviour

White and Black configured colours are being used in place of swapped foreground and background
In PowerShell:
image
In WSL:
image
In CMD:
image

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 25, 2020
@Starwort
Copy link
Author

Now I can set my black/white back properly 👀

@j4james
Copy link
Collaborator

j4james commented Jun 25, 2020

It looks like this is another variant of issue #2661. It'll be fixed by PR #6506.

@zadjii-msft
Copy link
Member

/dup #2661

@ghost
Copy link

ghost commented Jun 25, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jun 25, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 25, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants