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.

Sign up for GitHub

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

Jump to bottom

[BUG] Switching to legacy console and back makes all text invisible #5499

Closed
androidacy-user opened this issue Apr 23, 2020 · 5 comments
Closed

[BUG] Switching to legacy console and back makes all text invisible #5499

androidacy-user opened this issue Apr 23, 2020 · 5 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@androidacy-user
Copy link

androidacy-user commented Apr 23, 2020 •
edited
Loading

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.778]

Any other software?

Steps to reproduce

Switch to legacy console mode.
Restart cmd
Switch to new console.
Restart cmd

Expected behavior

No user visible changes

Actual behavior

Text is invisble.
@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 Apr 23, 2020
@DHowett-MSFT
Copy link
Contributor

  1. There’s no real reason to use legacy console mode; if you’re encountering a compatibility issue please let us know.
  2. This is a /dupe of Toggling Legacy console on and off enables Terminal colors but sets them to all black #2319

@ghost
Copy link

ghost commented Apr 23, 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 Apr 23, 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 Apr 23, 2020
@androidacy-user
Copy link
Author

  1. There’s no real reason to use legacy console mode; if you’re encountering a compatibility issue please let us know.
  2. This is a /dupe of Toggling Legacy console on and off enables Terminal colors but sets them to all black #2319

Tell an atom extension they need to update then. They have explicitly refused to update for the new console, but ubuntu WSL refuses to work with legacy.

@DHowett-MSFT
Copy link
Contributor

If you could tell me which atom extension, I would be glad to. They’re forcing users to reconfigure a critical part of their OS because of some weird ideology when it’d be easier for them to just update? I’d love to give them the what’s-what. Or, of course, if they also have compatibility concerns I’d be glad to get them fixed.

@androidacy-user
Copy link
Author

It's a terminal in the ide one, I don't have my laptop handy to check

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett-MSFT @androidacy-user