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.

Sign up for GitHub

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

Jump to bottom

Aclylic change to solid background after entering a space when using Cascadia Code PL font with PowerShell Core #7548

Closed
TheBlueSky opened this issue Sep 6, 2020 · 2 comments
Closed

Aclylic change to solid background after entering a space when using Cascadia Code PL font with PowerShell Core #7548

TheBlueSky opened this issue Sep 6, 2020 · 2 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@TheBlueSky
Copy link

Environment

Windows build number: 10.0.19041.0
Windows Terminal version: 1.2.2381.0

Steps to reproduce

  1. Set fontFace to Cascadia Code PL for PowerShell Core ("source": "Windows.Terminal.PowershellCore").
  2. Set useAcrylic to true.
  3. Set acrylicOpacity to any number.
  4. Launch Windows Terminal and open PowerShell Core (if it is not your default profile).
  5. Type anything with space; e.g., cd /

Expected behaviour

All the entered text has the same background, the one with Acrylic effect.

Actual behaviour

All the text from the space onwards has a solid background.

wt
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 6, 2020
@j4james
Copy link
Collaborator

j4james commented Sep 6, 2020

This is a PowerShell bug (see issue #6767). I believe it should be fixed if you upgrade PSReadLine. You can get the latest version by following the instructions here: https://github.com/PowerShell/PSReadLine#upgrading

@TheBlueSky
Copy link
Author

Thanks, @j4james.
I updated PSReadLine from v2.0.2 to v2.0.4, and I do not have the issue anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TheBlueSky @j4james