wsl bash color layer goes unwell, it's against my eyes.... #1673

Closed
opened 2026-01-30 22:33:21 +00:00 by claunia · 4 comments
Owner

Originally created by @charlesld on GitHub (Jun 14, 2019).

  • Your Windows build number:

Microsoft Windows [版本 10.0.18362.116]

  • bash version
C:\WINDOWS\system32>bash
charles@DESKTOP-3DSSNKC:/mnt/c/WINDOWS/system32$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic
charles@DESKTOP-3DSSNKC:/mnt/c/WINDOWS/system32$
  • What you're doing and what's happening:

just use wsl shell in jetbrain IDE(Idea pycharm goland..)

  • What's wrong / what should be happening instead:

after upgrade win10 to current version. then
strange color config when typed bash in the console.
image

can you see what I typed in the bash console?????????
but is works well in win+r -> cmd -> bash orwin+r -> bash
what I can do , or where I can restore the config?
ide just conf like this ,and no more conf can be set.
image

Originally created by @charlesld on GitHub (Jun 14, 2019). * Your Windows build number: > Microsoft Windows [版本 10.0.18362.116] * bash version ```shell C:\WINDOWS\system32>bash charles@DESKTOP-3DSSNKC:/mnt/c/WINDOWS/system32$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic charles@DESKTOP-3DSSNKC:/mnt/c/WINDOWS/system32$ ``` * What you're doing and what's happening: > just use wsl shell in **jetbrain** IDE(`Idea` `pycharm` `goland`..) * What's wrong / what should be happening instead: after upgrade win10 to current version. then **strange color config** when typed `bash` in the console. ![image](https://user-images.githubusercontent.com/23304239/59496729-a7b67e80-8ec4-11e9-8826-d6b912b052cf.png) **can you see what I typed in the bash console?????????** but is works well in `win+r -> cmd -> bash` or`win+r -> bash` what I can do , or where I can restore the config? ide just conf like this ,and no more conf can be set. ![image](https://user-images.githubusercontent.com/23304239/59497717-8bb3dc80-8ec6-11e9-9327-ded513cc85f1.png)
Author
Owner

@charlesld commented on GitHub (Jun 14, 2019):

another PC at home running in win10 [版本 10.0.18362.145] get same problem, which newly reinstalled os , and new jetbrain version.
Two computers are using same login id, and I wonder that , had I changed some termial color configs , and they were synced by the account?

@charlesld commented on GitHub (Jun 14, 2019): another PC at home running in win10 `[版本 10.0.18362.145]` get same problem, which newly reinstalled os , and new jetbrain version. Two computers are using same login id, and I wonder that , had I changed some termial color configs , and they were synced by the account?
Author
Owner

@zadjii-msft commented on GitHub (Jun 14, 2019):

@charlesld Does this repro in any environment on your PC other than the jetbrains IDE you're using? Does it happen in a normal conhost window (like the one created by cmd.exe, wsl.exe, powershell)? What about ConEmu/Hyper? VsCode's integrated terminal?

We don't really control what's displayed by the jetbrains terminal - IIRC they're using winpty as a backend for their terminal window.

If I had to guess, the "default background" color for the IDE's terminal is set to cyan, not black

@zadjii-msft commented on GitHub (Jun 14, 2019): @charlesld Does this repro in any environment on your PC other than the jetbrains IDE you're using? Does it happen in a normal conhost window (like the one created by cmd.exe, wsl.exe, powershell)? What about ConEmu/Hyper? VsCode's integrated terminal? We don't _really_ control what's displayed by the jetbrains terminal - IIRC they're using winpty as a backend for their terminal window. If I had to guess, the "default background" color for the IDE's terminal is set to cyan, not black
Author
Owner

@ghost commented on GitHub (Jun 18, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 18, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@ghost commented on GitHub (Jun 22, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 22, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1673