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

FiraCode character render issue #8659

New Issue
Closed
opened 2026-01-31 01:34:52 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 01:34:52 +00:00
Owner
Copy Link

Originally created by @K-E-N-W-A-Y on GitHub (May 29, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.264]
Windows Terminal version (if applicable): Version: 1.0.1401.0

Any other software?

WSL2 + ZSH (oh my zsh) + Starship Prompt

Steps to reproduce

Set Windows Terminal fontFace to Fira Code.

Expected behavior

Render Square character as it is.

Actual behavior

Windows Terminal doesn't render square character as it is BTW I use same Fira Code font in vscode & it renders all characters correctly

Windows Terminal:
image

VS Code (correct character render):
image

Originally created by @K-E-N-W-A-Y on GitHub (May 29, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Microsoft Windows [Version 10.0.19041.264] Windows Terminal version (if applicable): Version: 1.0.1401.0 Any other software? ``` WSL2 + ZSH (oh my zsh) + Starship Prompt # Steps to reproduce <!-- A description of how to trigger this bug. --> Set Windows Terminal fontFace to Fira Code. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Render Square character as it is. # Actual behavior <!-- What's actually happening? --> Windows Terminal doesn't render square character as it is BTW I use same Fira Code font in vscode & it renders all characters correctly Windows Terminal: ![image](https://user-images.githubusercontent.com/25846872/83216427-d9346280-a186-11ea-92c8-fc75b2d53904.png) VS Code (correct character render): ![image](https://user-images.githubusercontent.com/25846872/83216477-fbc67b80-a186-11ea-8731-1c939719f106.png)
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 01:34:52 +00:00
claunia commented 2026-01-31 01:34:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 29, 2020):

Can you share the codepoint of that square glyph? I don’t have “lsd” here to test with.

@DHowett commented on GitHub (May 29, 2020): Can you share the codepoint of that square glyph? I don’t have “lsd” here to test with.
claunia commented 2026-01-31 01:34:54 +00:00
Author
Owner
Copy Link

@K-E-N-W-A-Y commented on GitHub (May 29, 2020):

sorry, i don't know the exact codepoint for this square glyph. is there any way to get codepoint from this? so I can provide that :)

@K-E-N-W-A-Y commented on GitHub (May 29, 2020): sorry, i don't know the exact codepoint for this square glyph. is there any way to get codepoint from this? so I can provide that :)
claunia commented 2026-01-31 01:34:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 29, 2020):

It may help if you copy and paste it out of VSCode and terminal into a GitHub comment :)

@DHowett commented on GitHub (May 29, 2020): It may help if you copy and paste it out of VSCode and terminal into a GitHub comment :)
claunia commented 2026-01-31 01:34:54 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (May 29, 2020):

The code points for the characters that you are looking for can be found in https://github.com/Peltoche/lsd/blob/master/src/icon.rs . It seems that quite a lot of them are Private Use Area code points.

The error here is in the erroneous expectation that private use code points will be the same from font to font. The local fix is to make lsd stop (ab)using them and have it use the standardized Unicode characters with --icon-theme unicode.

Sadly, a lot more work could be done on lsd's Unicode mode. This is issue #10 for lsd and no-one has fleshed out the Unicode icon set beyond basic characters for file and folder. Please go to the lsd people and suggest a few.

@jdebp commented on GitHub (May 29, 2020): The code points for the characters that you are looking for can be found in https://github.com/Peltoche/lsd/blob/master/src/icon.rs . It seems that quite a lot of them are Private Use Area code points. The error here is in the erroneous expectation that _private use_ code points will be the same from font to font. The local fix is to make `lsd` _stop (ab)using them_ and have it use the _standardized_ Unicode characters with `--icon-theme unicode`. Sadly, a lot more work could be done on `lsd`'s Unicode mode. This is [issue #10 for `lsd`](https://github.com/Peltoche/lsd/issues/10) and no-one has fleshed out the Unicode icon set beyond basic characters for file and folder. Please go to the `lsd` people and suggest a few.
claunia commented 2026-01-31 01:34:54 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (May 29, 2020):

I can concur that this is more of a font issue. A little debugging told me that is a mixed usage of U+F115 and U+E27C, which are both considered illegal Unicode characters.

If I'm using Cascadia Code, the lsd result looks better:

image

However with Fira Code, this will happen:

image

@skyline75489 commented on GitHub (May 29, 2020): I can concur that this is more of a font issue. A little debugging told me that is a mixed usage of `U+F115` and `U+E27C`, which are both considered illegal Unicode characters. If I'm using Cascadia Code, the `lsd` result looks better: ![image](https://user-images.githubusercontent.com/4710575/83241096-eaa05d80-a1cc-11ea-8fd4-fce77e880fd8.png) However with Fira Code, this will happen: ![image](https://user-images.githubusercontent.com/4710575/83241163-04da3b80-a1cd-11ea-922c-38390dcc8053.png)
claunia commented 2026-01-31 01:34:55 +00:00
Author
Owner
Copy Link

@K-E-N-W-A-Y commented on GitHub (May 29, 2020):

It may help if you copy and paste it out of VSCode and terminal into a GitHub comment :)

VS Code: 
Terminal: 

@K-E-N-W-A-Y commented on GitHub (May 29, 2020): > It may help if you copy and paste it out of VSCode and terminal into a GitHub comment :) VS Code:  Terminal: 
claunia commented 2026-01-31 01:34:55 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 2, 2020):

Well, I've got some bad news. That's U+E60B, which is firmly in the private use area. Fira Code doesn't have a glyph for that codepoint, so what you're seeing is the NOGLYPH character. It looks like a box, sometimes a ?, sometimes a <?>, and certain layout engines will display it as a cute box with the characters E 6 0 B in it.

In all cases, it's the same issue: there's no glyph there. lsd seems to require a special font.

Resolving as external. 😄

@DHowett commented on GitHub (Jun 2, 2020): Well, I've got some _bad news_. That's `U+E60B`, which is firmly in the private use area. Fira Code doesn't have a glyph for that codepoint, so what you're seeing is the NOGLYPH character. It looks like a box, sometimes a `?`, sometimes a `<?>`, and certain layout engines will display it as a cute box with the characters `E 6 0 B` in it. In all cases, it's the same issue: there's no glyph there. lsd seems to require a special font. Resolving as external. :smile:
claunia commented 2026-01-31 01:34:55 +00:00
Author
Owner
Copy Link

@K-E-N-W-A-Y commented on GitHub (Jun 3, 2020):

@DHowett @skyline75489 i changed windows terminal font to patched Cascadia code font from nerd fonts. now icons look better.

image

thanks in advance for the help <3 :)

@K-E-N-W-A-Y commented on GitHub (Jun 3, 2020): @DHowett @skyline75489 i changed windows terminal font to [patched Cascadia code font](https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/CascadiaCode/complete/Caskaydia%20Cove%20Regular%20Nerd%20Font%20Complete%20Windows%20Compatible.ttf) from nerd fonts. now icons look better. ![image](https://user-images.githubusercontent.com/25846872/83583631-76fea780-a562-11ea-9e9c-e9045674a8da.png) thanks in advance for the help <3 :)
claunia commented 2026-01-31 01:34:55 +00:00
Author
Owner
Copy Link

@mrbeardad commented on GitHub (Aug 29, 2020):

image
Why my nerdfont icon is so small?

@mrbeardad commented on GitHub (Aug 29, 2020): ![image](https://user-images.githubusercontent.com/54128430/91625696-11dd1580-e9dc-11ea-86f0-b8131d3feff5.png) Why my nerdfont icon is so small?
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 Resolution-External
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#8659
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?