-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
PowerShell colors weird after update to 1.22.2408.23002 (preview) #17854
Comments
Which version of PowerShell are you using? |
It's the built-in one called "PowerShell" (not PWSH); I'm on Windows 10. In the user environment I have |
This is an intentional regression we introduced to make many other major improvements possible, including sixels. It was removed in #17666. You can fix the issue by running The issue happens because Windows 10 ships with PSReadLine that contains a bug where the attributes are incorrect. The issue was fixed in the following PR which ships with Windows 11: PowerShell/PSReadLine#1626 |
Thanks for the info. It's no big deal to me. I'm no fan of PowerShell (in any form) and I do have an up-to-date (?) PWSH which does not exhibit the behavior in question. If I hide WT's "PowerShell" profile, I won't be tempted to run the old one. |
I've updated my comment with relevant links. I'll close this issue for now since I broke it intentionally (see #17666). (Side note: It can theoretically be fixed by adding a new |
I have changed nothing here except for installing the latest WT builds, WindowsTerminal 1.21.2408.23001 and WindowsTerminal 1.22.2408.23002 (preview). The following is new behavior. It only happens in the 1.22 preview (not in 1.21 or in previous releases of any kind).
Whenever text on a command line in progress is erased (backspace, Esc, when scrolling through the history) the background color is replaced by black.
Before pressing Esc:
After pressing Esc:
The text was updated successfully, but these errors were encountered: