-
Notifications
You must be signed in to change notification settings - Fork 299
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
PSReadLine doesn't work properly with Windows Terminal's background image #1842
Comments
this is a duplicate of #830, and only happens if you're using the "dotnet global" tool version of PowerShell and haven't updated PSReadline. |
@DHowett Yes, I have "dotnet global" tool version of PowerShell core, but I think my PSReadLine is already up-date? |
Hmm, looking over the releases, it looks like that fix was made after the beta release and released as 2.0.3; I don't see another beta release after that, so it looks like it hasn't been rolled into a beta branch just yet. |
@vexx32 looks like that's it, I uninstalled the pre-release version of PSReadLine and issue has been fixed. |
Environment
Steps to reproduce & Expected behavior & Actual behavior
(From PowerShell/PowerShell#13720)
I think the screenshot below should be self-explanatory, but let me explain more precisely.
Windows Terminal allows us to set a background image, then it will replace the area occupied by the original background color with the background image.
But when I'm typing commands that contain spaces, the background color of text returned to be the original background color, instead of being "transparent" (or more preciesly, instead of displaying the content of background image).
It only occurs when I'm typing commands, looks like this problem won't be triggered when I'm writing a string literal, even if it contains spaces, as shown in the screenshot.
If I unload PSReadLine module, the issue won't occur anymore.
The text was updated successfully, but these errors were encountered: