You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is what it looks like with my current config:
Please notice the tiny little black parts between source and 0ms resp. pwsh and the current time.
To get rid of them, I tried "terminal_background": "transparent", which looks like this:
The config parameter "terminal_background" seems to be the correct one for my needs, because when using "terminal_background": "#2e9599", it looks like this:
@mu88 a few things, "terminal_background": "transparent" is not supported, it needs be an actual color. Without specifying that color, our engine uses transparent by itself. The fact that you see black triangles is because WT (and depending on the renderer) has issues with inverted ANSI. You can try their new Atlas render engine to see if this is already resolved, check the preview of WT. Setting the background to #2e9599 is handled correctly as that one indeed prints the correct color, but your terminal has a background color of #393939.
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues.
If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
This is what it looks like with my current config:
Please notice the tiny little black parts between source and 0ms resp. pwsh and the current time.
To get rid of them, I tried
"terminal_background": "transparent"
, which looks like this:The config parameter
"terminal_background"
seems to be the correct one for my needs, because when using"terminal_background": "#2e9599"
, it looks like this:Theme
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output
The text was updated successfully, but these errors were encountered: