starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 02:23:46 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 02:23:46 +00:00
Owner
Copy Link

Originally created by @TheBlueSky on GitHub (Sep 6, 2020).

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

Originally created by @TheBlueSky on GitHub (Sep 6, 2020). # Environment ```none 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"`). 1. Set `useAcrylic` to `true`. 1. Set `acrylicOpacity` to any number. 1. Launch Windows Terminal and open PowerShell Core (if it is not your default profile). 1. 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](https://user-images.githubusercontent.com/807685/92321587-72e39980-f02b-11ea-995b-0370b793c9d0.png)
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 02:23:46 +00:00
claunia commented 2026-01-31 02:23:46 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (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

@j4james commented on GitHub (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
claunia commented 2026-01-31 02:23:47 +00:00
Author
Owner
Copy Link

@TheBlueSky commented on GitHub (Sep 6, 2020):

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

@TheBlueSky commented on GitHub (Sep 6, 2020): Thanks, @j4james. I updated PSReadLine from v2.0.2 to v2.0.4, and I do not have the issue anymore.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10518
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?