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

Closed
opened 2026-01-31 01:08:21 +00:00 by claunia · 5 comments
Owner

Originally created by @androidacy-user on GitHub (Apr 23, 2020).

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.

Originally created by @androidacy-user on GitHub (Apr 23, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.778] Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Switch to legacy console mode. Restart cmd Switch to new console. Restart cmd # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> No user visible changes # Actual behavior <!-- What's actually happening? --> Text is invisble.
claunia added the Resolution-Duplicate label 2026-01-31 01:08:21 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 23, 2020):

  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 Bug Report: Ctrl-W for cut not working in Emacs in Ubuntu-Terminal (#2319)
@DHowett-MSFT commented on GitHub (Apr 23, 2020): 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 #2319
Author
Owner

@ghost commented on GitHub (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 commented on GitHub (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!
Author
Owner

@androidacy-user commented on GitHub (Apr 23, 2020):

  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 Bug Report: Ctrl-W for cut not working in Emacs in Ubuntu-Terminal (#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.

@androidacy-user commented on GitHub (Apr 23, 2020): > 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 #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.
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 23, 2020):

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.

@DHowett-MSFT commented on GitHub (Apr 23, 2020): 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.
Author
Owner

@androidacy-user commented on GitHub (Apr 24, 2020):

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

@androidacy-user commented on GitHub (Apr 24, 2020): It's a terminal in the ide one, I don't have my laptop handy to check
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7597