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

Glyphs from U+f900 to U+fad9 have wrong extra space in certain condition when we use colors #17750

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

Originally created by @ahmedwelhakim on GitHub (Jun 20, 2022).

Windows Terminal version

1.13.11432.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

First we need to install Nerd Font, (I tesed with FantasqueSansMono NF, and CaskaydiaCove NF)

After installing it and use the font in the Windows Terminal, then we can print any glyphs that there hex range from U+f900 to U+fad9 with any color and Then putting any character next to it BUT with different color.
The script code for that is very simple:

Method 1 using ANSI escape sequence color

$col = 15
for ($i = 0xf900-$col*3; $i -lt 0xfaff+$col*3; $i+=$j) {
    for($j = 0; $j - lt $col; $j++){
        Write-Host("{0}`e[38;2;0;255;10m{1}`e[0m{2}{3:x}   "  -f "[",[char]($i+$j), "]",($i+$j)) -NoNewLine 
    }
    Write-Host('')
}

OR

Method 2 using -ForegroundColor parameter

$col = 15
for ($i = 0xf900-$col*3; $i -lt 0xfaff+$col*3; $i+=$j) {
    for($j = 0;$j -lt $col ;$j++){
        Write-Host("{0}{1}" -f '(',[char]($i+$j)) -NoNewLine -ForegroundColor Red 
        Write-Host("{0}{1:x}  " -f ')', ($i + $j) ) -NoNewLine -ForegroundColor Green
    }
    Write-Host('')
}

Method 3 which is behaving half correctly but in certain condition

when we don't change the color and we must continue with the same color IF WE CHANGE IT the first character after changing the color will be spaced

$col = 15
for ($i = 0xf900-$col*3; $i -lt 0xfaff+$col*3; $i+=$j) {
    for($j = 0;$j -lt $col ;$j++){
        Write-Host("{0}`e[38;2;0;255;10m{1}{2}{3:x}   "  -f "[",[char]($i+$j), "]",($i+$j)) -NoNewLine 
    }
    Write-Host('')
}

Expected Behavior

Method 3 output :

method 3

Here as we can see when we don't change the color after the glyph so there is no space, and that should be the normal case even when we change the color.

BUT

if I change the color of hex there will be an extra space but before the hex not the square bracket as the square bracket with the same color of glyph as in the screen shots in the actual behavior down.

Actual Behavior

Method 1 Output

case1 method1

We can see here there is space after every glyph in first color transition.

Method 2 Output as above but with using -Foreground parameter.

case1 method2

shifting the space location by using same color of glyph then change it

case3

We can notice that the glyph is green colored and "]" is also green so no space between them when we change the color the space became before the changed text color

Here is another proof that it depends on changing the color

case 3 wrong

There should be no space between hex and "dummy"

Originally created by @ahmedwelhakim on GitHub (Jun 20, 2022). ### Windows Terminal version 1.13.11432.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce First we need to install Nerd Font, (I tesed with FantasqueSansMono NF, and CaskaydiaCove NF) After installing it and use the font in the Windows Terminal, then we can print any glyphs that there hex range from U+f900 to U+fad9 with any **color** and **Then** putting any character next to it **BUT** with different color. The script code for that is very simple: ## Method 1 using ANSI escape sequence color ``` $col = 15 for ($i = 0xf900-$col*3; $i -lt 0xfaff+$col*3; $i+=$j) { for($j = 0; $j - lt $col; $j++){ Write-Host("{0}`e[38;2;0;255;10m{1}`e[0m{2}{3:x} " -f "[",[char]($i+$j), "]",($i+$j)) -NoNewLine } Write-Host('') } ``` ### OR ## Method 2 using `-ForegroundColor` parameter ``` $col = 15 for ($i = 0xf900-$col*3; $i -lt 0xfaff+$col*3; $i+=$j) { for($j = 0;$j -lt $col ;$j++){ Write-Host("{0}{1}" -f '(',[char]($i+$j)) -NoNewLine -ForegroundColor Red Write-Host("{0}{1:x} " -f ')', ($i + $j) ) -NoNewLine -ForegroundColor Green } Write-Host('') } ``` ## Method 3 which is behaving half correctly **but in certain condition** when we don't change the color and we must continue with the same color **IF WE CHANGE IT** the first character after changing the color will be spaced ``` $col = 15 for ($i = 0xf900-$col*3; $i -lt 0xfaff+$col*3; $i+=$j) { for($j = 0;$j -lt $col ;$j++){ Write-Host("{0}`e[38;2;0;255;10m{1}{2}{3:x} " -f "[",[char]($i+$j), "]",($i+$j)) -NoNewLine } Write-Host('') } ``` ### Expected Behavior ## Method 3 output : ![method 3](https://user-images.githubusercontent.com/53128020/174503563-66f1b436-8400-48b0-89fa-f0ebb733d4c1.png) Here as we can see when we don't change the color after the glyph so there is no space, and that should be the normal case even when we change the color. ### BUT if I change the color of hex there will be an extra space but before the hex not the square bracket as the square bracket with the same color of glyph as in the screen shots in the actual behavior down. ### Actual Behavior ## Method 1 Output ![case1 method1](https://user-images.githubusercontent.com/53128020/174503001-c48dab7d-3fcf-4b24-94fb-b468469a99aa.png) We can see here there is space after every glyph in first color transition. ## Method 2 Output as above but with using `-Foreground` parameter. ![case1 method2](https://user-images.githubusercontent.com/53128020/174503056-0f9248ec-7470-43a1-b6a1-f2991b85b75c.png) ## shifting the space location by using same color of glyph then change it ![case3](https://user-images.githubusercontent.com/53128020/174503861-d3b5ddd9-1824-426b-8a3d-7403f11c1719.png) We can notice that the glyph is green colored and "]" is also green so no space between them when we change the color the space became before the changed text color ## Here is another proof that it depends on changing the color ![case 3 wrong](https://user-images.githubusercontent.com/53128020/174504072-63818086-fd77-4d22-91e5-894b7485915d.png) There should be no space between hex and "dummy"
claunia added the Issue-BugResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 05:52:15 +00:00
claunia commented 2026-01-31 05:52:16 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jun 20, 2022):

I haven't looked at your code in detail, so I'm not sure why you're seeing different results based on the color usage, but either way I wouldn't expect that glyph range to work in Nerd Fonts. Those positions are reserved for CJK Compatibility Ideographs and shouldn't have been used by them. This is a know issue, and is apparently planned to be fixed in version 3.0.

Some relevant links:

@j4james commented on GitHub (Jun 20, 2022): I haven't looked at your code in detail, so I'm not sure why you're seeing different results based on the color usage, but either way I wouldn't expect that glyph range to work in Nerd Fonts. Those positions are reserved for CJK Compatibility Ideographs and shouldn't have been used by them. This is a know issue, and is apparently planned to be fixed in version 3.0. Some relevant links: - https://github.com/ryanoasis/nerd-fonts/issues/574 - https://github.com/ryanoasis/nerd-fonts/issues/637 - https://github.com/ryanoasis/nerd-fonts/discussions/716
claunia commented 2026-01-31 05:52:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 20, 2022):

Thanks for the quick triage, James!

@DHowett commented on GitHub (Jun 20, 2022): Thanks for the quick triage, James!
claunia commented 2026-01-31 05:52:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 20, 2022):

/dup https://github.com/ryanoasis/nerd-fonts/issues/637

@DHowett commented on GitHub (Jun 20, 2022): /dup https://github.com/ryanoasis/nerd-fonts/issues/637
claunia commented 2026-01-31 05:52:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 20, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Jun 20, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
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-Bug Needs-Tag-Fix 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#17750
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?