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

Kubernetes helm symbol ⎈ (U+2388) is too small #8126

New Issue
Closed
opened 2026-01-31 01:21:19 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 01:21:19 +00:00
Owner
Copy Link

Originally created by @gitfool on GitHub (May 13, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 0.11.1333.0

Steps to reproduce

Compare the Kubernetes helm symbol ⎈ (U+2388) in Visual Studio Code & Windows Terminal.

Expected behavior

The symbol should be double width.

Actual behavior

The symbol is displayed using single width and is too small.

Visual Studio Code:
image

Windows Terminal:
image

Originally created by @gitfool on GitHub (May 13, 2020). # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 0.11.1333.0 ``` * [Nerd Fonts](https://www.nerdfonts.com/) [patched font](https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/FiraCode) for [Fira Code](https://github.com/tonsky/FiraCode) # Steps to reproduce Compare the Kubernetes helm symbol ⎈ (U+2388) in Visual Studio Code & Windows Terminal. # Expected behavior The symbol should be double width. # Actual behavior The symbol is displayed using single width and is too small. Visual Studio Code: ![image](https://user-images.githubusercontent.com/750121/81863573-8de35700-95bf-11ea-9f36-92b86bb761cd.png) Windows Terminal: ![image](https://user-images.githubusercontent.com/750121/81863708-bc613200-95bf-11ea-8643-7dc35ff0e4d3.png) * Changed in https://github.com/tonsky/FiraCode/commit/af1c556584c5679c5b8f5188441e8cfd2ee00c54
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:21:19 +00:00
claunia commented 2026-01-31 01:21:20 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 14, 2020):

Here's what U+2388 looks like in XTerm, Gnome Terminal, Konsole, Alacritty, Kitty, and Mintty.

image

Unless there's been a recent change to the width in the latest Unicode standard, I think it's probably meant to be narrow.

@j4james commented on GitHub (May 14, 2020): Here's what `U+2388` looks like in XTerm, Gnome Terminal, Konsole, Alacritty, Kitty, and Mintty. ![image](https://user-images.githubusercontent.com/4181424/81874860-ca3e9500-9576-11ea-8bbe-47421f00762a.png) Unless there's been a recent change to the width in the latest Unicode standard, I think it's probably meant to be narrow.
claunia commented 2026-01-31 01:21:20 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 14, 2020):

I agree.

I hate to call others out, but these Nerd Fonts are stomping all over the "unicode private use area" and expecting everybody to, well, treat them the same way. Those areas are "private use" for a reason :/

EDIT: So, 2588 is absolutely not in the PUA. I'm sorry about that. Read below for more details on why we think this is "hard" 😄

@DHowett-MSFT commented on GitHub (May 14, 2020): I agree. I hate to call others out, but these Nerd Fonts are stomping _all over_ the "unicode private use area" and expecting everybody to, well, treat them the same way. Those areas are "private use" for a reason :/ EDIT: So, 2588 is absolutely not in the PUA. I'm sorry about that. Read below for more details on why we think this is "hard" :smile:
claunia commented 2026-01-31 01:21:21 +00:00
Author
Owner
Copy Link

@gitfool commented on GitHub (May 14, 2020):

To be fair, I don't think this has anything to do with Nerd Fonts. The symbol is coming straight from Fira Code, unless I'm missing something.

As I linked to above, the Fira Code font has defined the symbol as double width. Shouldn't that be respected?

@gitfool commented on GitHub (May 14, 2020): To be fair, I don't think this has anything to do with Nerd Fonts. The symbol is coming straight from Fira Code, unless I'm missing something. As I linked to above, the Fira Code font has defined the symbol as double width. Shouldn't that be respected?
claunia commented 2026-01-31 01:21:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 14, 2020):

Ah, it's also fair that 2588 isn't IN the PUA. Sorry about that.

So, this comes up a lot. It's... not pleasant.

Applications connected to the client side of a console (or terminal!) need to be able to do column-counting. To do so, most of them either use inbuilt character tables or something like wcwidth (from libc). It's not a great API, but it is the one we have.

Unfortunately, there's no requirement that a character be presented. Anywhere! Subsequently, there's no affordance in wcwidth for a "presentation" measurement, like the one that would come from a font. The only thing that can be used to make the size decision for a codepoint is the intrinsic specified-in-the-Unicode-standard properties of that codepoint.

@DHowett-MSFT commented on GitHub (May 14, 2020): Ah, it's also fair that 2588 isn't IN the PUA. Sorry about that. So, this comes up a lot. It's... not pleasant. Applications connected to the client side of a console (or terminal!) need to be able to do column-counting. To do so, most of them either use inbuilt character tables _or_ something like `wcwidth` (from libc). It's not a great API, but it is the one we have. Unfortunately, there's no requirement that a character be presented. Anywhere! Subsequently, there's no affordance in `wcwidth` for a "presentation" measurement, like the one that would come from a font. The only thing that can be used to make the size decision for a codepoint is the intrinsic specified-in-the-Unicode-standard properties of that codepoint.
claunia commented 2026-01-31 01:21:21 +00:00
Author
Owner
Copy Link

@gitfool commented on GitHub (May 14, 2020):

That makes sense. Thanks for the clarification!

@gitfool commented on GitHub (May 14, 2020): That makes sense. Thanks for the clarification!
claunia commented 2026-01-31 01:21:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 14, 2020):

Sorry -- consider this a ramble. You're not required to read it 😄

Consider the case of Kubernetes sitting at the remote end of an SSH session. Say something prints the ⎈ symbol and wants to determine how much space is left in the line...

It's over SSH, and very far removed from the presentation surface that might be making the decision on how big it is. That's not a tenable position for it to be in, because it can't make that space determination without information known only to the application sitting on the other end of its PTY.

Even if we, and the rest of the text-mode community, plumbed through support for glyph presentation impacting width, who would answer that question?

+----------+
|          |
| Terminal |
|          |
+-+------+-+
  |      ^
  v      |
+-+------+-+
|          |
| ssh.exe  |
|          |
+-+------+-+
  |      ^
  v      |
+-+------+-+     +----------+     +----------+
|          |     |          |     |          |
|   sshd   +<----+ unix pty +<----+ K8s CLI  |
|          |     |          |     |          |
+----------+     +----------+     +----------+

Any determination would have to make it through all of those layers and back down, synchronously, when the K8s CLI asks how big a glyph is.

This is a hot button topic over on the terminal working group tracker! 😁

@DHowett-MSFT commented on GitHub (May 14, 2020): Sorry -- consider this a ramble. You're not required to read it :smile: Consider the case of Kubernetes sitting at the remote end of an SSH session. Say something prints the ⎈ symbol and wants to determine how much space is left in the line... It's over SSH, and very far removed from the presentation surface that might be making the decision on how big it is. That's not a tenable position for it to be in, because it can't make that space determination without information known only to the application sitting on the other end of its PTY. Even if we, and the rest of the text-mode community, plumbed through support for glyph presentation impacting width, who would answer that question? ``` +----------+ | | | Terminal | | | +-+------+-+ | ^ v | +-+------+-+ | | | ssh.exe | | | +-+------+-+ | ^ v | +-+------+-+ +----------+ +----------+ | | | | | | | sshd +<----+ unix pty +<----+ K8s CLI | | | | | | | +----------+ +----------+ +----------+ ``` Any determination would have to make it through all of those layers and back down, synchronously, when the K8s CLI asks how big a glyph is. This is a hot button topic over on the terminal working group tracker! 😁
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 Issue-Question Needs-Tag-Fix Resolution-Answered
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#8126
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?