Equals Sign Not Rendering in Powershell Core Tabs #4996

Closed
opened 2026-01-31 00:02:32 +00:00 by claunia · 2 comments
Owner

Originally created by @iUnknwn on GitHub (Nov 14, 2019).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.6.2951.0

Any other software? PowerShell 6. 

PSVersionTable:
Name                           Value
----                           -----
PSVersion                      6.2.3
PSEdition                      Core
GitCommitId                    6.2.3
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Steps to reproduce

The equals sign does not appear in certain operations in PowerShell core windows.

Typing: $a = 4 results in this:
image

They render normally as part of strings:
image

Expected behavior

The equals sign renders normally, as it does on non-pwsh Windows.

The same input in the Powershell tab works normally:
image

Additional Notes:
Changing the font settings appeared to have no effect. For reference, here is the entry for Powershell Core in my settings.json:

        {
            "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
            "hidden": false,
            "name": "PowerShell Core",
            "source": "Windows.Terminal.PowershellCore",
            "colorScheme": "Solarized Dark",
            "fontFace": "Cascadia Code",
            "fontSize": 10,
            "cursorShape": "bar"
        }
Originally created by @iUnknwn on GitHub (Nov 14, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.6.2951.0 Any other software? PowerShell 6. PSVersionTable: Name Value ---- ----- PSVersion 6.2.3 PSEdition Core GitCommitId 6.2.3 OS Microsoft Windows 10.0.18363 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0 ``` # Steps to reproduce The equals sign does not appear in certain operations in PowerShell core windows. Typing: `$a = 4` results in this: ![image](https://user-images.githubusercontent.com/1129122/68818151-e8afec00-0638-11ea-925c-c9d7b14aad08.png) They render normally as part of strings: ![image](https://user-images.githubusercontent.com/1129122/68818203-15640380-0639-11ea-9205-a46e6a285ae8.png) # Expected behavior The equals sign renders normally, as it does on non-pwsh Windows. The same input in the Powershell tab works normally: ![image](https://user-images.githubusercontent.com/1129122/68818233-30cf0e80-0639-11ea-8b39-6d8a11d90f16.png) Additional Notes: Changing the font settings appeared to have no effect. For reference, here is the entry for Powershell Core in my settings.json: ``` { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell Core", "source": "Windows.Terminal.PowershellCore", "colorScheme": "Solarized Dark", "fontFace": "Cascadia Code", "fontSize": 10, "cursorShape": "bar" } ```
claunia added the Resolution-Duplicate label 2026-01-31 00:02:32 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Nov 14, 2019):

This is, you might be puzzled to learn, a /dupe of #293 and #2054 (although instead of Light/brightWhite it's Dark/brightBlack)

@DHowett-MSFT commented on GitHub (Nov 14, 2019): This is, you might be puzzled to learn, a /dupe of #293 and #2054 (although instead of Light/brightWhite it's Dark/brightBlack)
Author
Owner

@ghost commented on GitHub (Nov 14, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 14, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4996