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

Windows - Integrated Terminal running Ubuntu resets white to blue (ansiBlue) #45015

Closed
tomjaimz opened this issue Mar 4, 2018 · 1 comment
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label

Comments

@tomjaimz
Copy link

tomjaimz commented Mar 4, 2018

  • VSCode Version: 1.20.1
  • OS Version: Windows 10.0.16299.24

I have tried reinstalling VS Code several times and have also completely removed Bash and installed Ubuntu from the Microsoft Store. I have wiped both my AppData\Roaming\Code and my .vscode directories.

Whenever my Bash terminal within the Integrated Terminal of VS Code encounters a colour and is supposed to return to white, it returns instead to blue. Then anything that is supposed to be blue is white. The only way around it I have found is to defined ansiBlue as a white colour in the user settings (which means that then my terminal cannot display blue correctly).

Running echo -e "\e[37m" will also get me back to white, but as soon as the system encounters another colour code, and then a reset, it's back to blue. Most tellingly, echo -e "\x1b[0m" takes me from white to blue.

Here is a simple example:

blue

This does not happen when running Ubuntu/Bash from outside of VS Code.

Does this issue occur when all extensions are disabled?: Yes

@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Mar 4, 2018
@tomjaimz tomjaimz changed the title Windows - Integrated Terminal running Ubuntu shows white as blue (ansiBlue) Windows - Integrated Terminal running Ubuntu resets white to blue (ansiBlue) Mar 4, 2018
@Tyriar
Copy link
Member

Tyriar commented Mar 4, 2018

Duplicate #40327

@Tyriar Tyriar closed this as completed Mar 4, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 4, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

2 participants