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

Inconsistent formatting in integrated terminal (powershell formatting 'bleed-through') #40190

Closed
confusingbits opened this issue Dec 14, 2017 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@confusingbits
Copy link

confusingbits commented Dec 14, 2017

  • VSCode Version: 1.18.1
  • OS Version: Windows 10: 1709

I have been having this issue with the vscode integrated terminal for probably 6 months now. The terminal appears to become 'corrupted' while running scripts like webpack or jest running in the terminal. Powershell formatting settings appear to 'bleed through' and make the terminal unreadable. I have reinstalled VScode with no effect as well as reset powershell's formatting settings with 'Set-PSReadlineOption -ResetTokenColors` to no effect.

I am not using any terminal setting that I am aware of and using Dark+ (default dark), which I believe to be completely stock. (I've tried every setting that I can think of.) The problem will persist with other themes.

Here is what it looks like:

bug

I believe that I have identified a workaround by enabling 'legacy mode' in powershell, which can be done by opening a full powershell and choosing properties > options > 'Use legacy console (requires relaunch)'.

As demonstrated here:

console fix

This appears to resolve the immediate issue, however, if one attempts to use bash, you will now receive the error: 'Unsupported console settings. In order to use this feature the legacy console must be disabled.'

Reproduces without extensions: Yes

@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Dec 14, 2017
@Tyriar
Copy link
Member

Tyriar commented Dec 14, 2017

@rprichard this seems to be a pretty common issue, have you seen this before?

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Dec 14, 2017
@Tyriar Tyriar added this to the Backlog milestone Dec 14, 2017
@Tyriar
Copy link
Member

Tyriar commented Dec 28, 2017

Let's track this in #40327

@Tyriar Tyriar closed this as completed Dec 28, 2017
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 28, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants