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

Wrong foreground color for some powerline symbols on Windows Terminal with acrylic background enabled. #1556

Closed
1 task done
philippetev opened this issue Jan 11, 2022 · 2 comments
Assignees
Labels
🐛 bug Something isn't working

Comments

@philippetev
Copy link

philippetev commented Jan 11, 2022

Code of Conduct

  • I agree to follow this project's Code of Conduct

What happened?

Windows 10, Powershell 7.2.1, Windows Terminal 1.11.3471.0

The foreground color for one of the powerline symbols doesn't seems to be the correct one. Looks like hard-coded.

Black FG on White BG:
no-theme-black_on_white
White FG on black BG
no-theme-white_on_black

The shots above are taken with acrylic background enabled at 80%. There is not such issue if the acrylic background is off.
Note that the other bordering powerline symbols have no such issue with the acrylic background.

Theme

No theme / the default one.

What OS are you seeing the problem on?

Windows

Which shell are you using?

powershell

Log output

Version: 6.44.1

Segments:

ConsoleTitle(true) -   0 ms -
session(true)  -   0 ms -  Filip.Petev@WHA0385711 
path(true)     -   1 ms -   ~ 
git(false)     -   5 ms -
battery(false) -   1 ms -
node(false)    -   0 ms -
shell(true)    -   0 ms -  ﲵ pwsh 
root(false)    -   0 ms -
text(true)     -   0 ms -  NO CONFIG 
exit(true)     -   0 ms -   

Run duration: 8.9618ms

Logs:

2022/01/11 14:41:20 debug: getenv
C:\Users\Filip.Petev\AppData\Local
2022/01/11 14:41:20 getenv duration: 0s, args: LOCALAPPDATA
2022/01/11 14:41:20 getCachePath duration: 0s, args:
2022/01/11 14:41:20 getArgs duration: 0s, args:
2022/01/11 14:41:20 getArgs duration: 0s, args:
2022/01/11 14:41:20 getShellName duration: 11.1076ms, args:
2022/01/11 14:41:20 debug: getenv

2022/01/11 14:41:20 getenv duration: 0s, args: OMP_CACHE_DISABLED
2022/01/11 14:41:20 isRunningAsRoot duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getShellName duration: 0s, args:
2022/01/11 14:41:20 getCurrentUser duration: 0s, args:
2022/01/11 14:41:20 getHostName duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 debug: getenv

2022/01/11 14:41:20 getenv duration: 0s, args: SSH_CONNECTION
2022/01/11 14:41:20 debug: getenv

2022/01/11 14:41:20 getenv duration: 0s, args: SSH_CLIENT
2022/01/11 14:41:20 getCurrentUser duration: 0s, args:
2022/01/11 14:41:20 getRuntimeGOOS duration: 0s, args:
2022/01/11 14:41:20 getHostName duration: 0s, args:
2022/01/11 14:41:20 debug: getenv

2022/01/11 14:41:20 getenv duration: 0s, args: POSH_SESSION_DEFAULT_USER
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getArgs duration: 0s, args:
2022/01/11 14:41:20 getRuntimeGOOS duration: 0s, args:
2022/01/11 14:41:20 getRuntimeGOOS duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getRuntimeGOOS duration: 0s, args:
2022/01/11 14:41:20 stackCount duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getRuntimeGOOS duration: 0s, args:
2022/01/11 14:41:20 error: hasCommand
exec: "git.exe": executable file not found in %PATH%
2022/01/11 14:41:20 hasCommand duration: 5.9565ms, args: git.exe
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getBatteryInfo duration: 1.9951ms, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getShellName duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 isRunningAsRoot duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 isRunningAsRoot duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getPathSeperator duration: 0s, args:
2022/01/11 14:41:20 getShellName duration: 0s, args:
2022/01/11 14:41:20 getCurrentUser duration: 0s, args:
2022/01/11 14:41:20 getHostName duration: 0s, args:
2022/01/11 14:41:20 getcwd duration: 0s, args:
2022/01/11 14:41:20 lastErrorCode duration: 0s, args:
@philippetev philippetev added the 🐛 bug Something isn't working label Jan 11, 2022
@JanDeDobbeleer
Copy link
Owner

@philippetev that's a bug in Windows Terminal.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants