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

Terminal color output not displaying as expected #6711

Closed
laballab opened this issue Jun 29, 2020 · 3 comments
Closed

Terminal color output not displaying as expected #6711

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

Comments

@laballab
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.900]
Windows Terminal version (if applicable): Version: 1.0.1401.0

All steps/tests are done in a git-bash profile in windows terminal. 

Steps to reproduce

I can consistently reproducing this issue by running k9s with invalid kubeconfig. K9s will output a red-colored warning regarding this which is not rendered properly on windows terminal.

Expected behavior

A colorful error message warning us about the invalid kubeconfig:
image

Actual behavior

Windows terminal is not rendering the color output properly:
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 29, 2020
@laballab
Copy link
Author

It seems the color commands are being interpreted as utf-8 arrows for some reason.. It's strange this bug isn't present in the bash prompt as the same color commands are used there and the colors are rendered properly.

@DHowett
Copy link
Member

DHowett commented Jun 29, 2020

Huh, thanks for the report.

This is the same root cause as #6634

More info at #6634 (comment)

/dup #6634
Unfortunately, this is an application bug ☹️

@ghost
Copy link

ghost commented Jun 29, 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 29, 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 29, 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

2 participants