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

Make large numbers easier to read #20101

New Issue
Closed
opened 2026-01-31 07:03:35 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:03:35 +00:00
Owner
Copy Link

Originally created by @mlongtin0 on GitHub (Jun 16, 2023).

Description of the new feature/enhancement

Large numbers like "16000000" are hard to read in a monitor. Is it 1.6, 16 or 160 millions? I end up trying to select groups of three to make sense of it.

I would like to propose to italicize or bold alternating groups, like this: 16000000 or 16000000
This would be enough to make it easier to read. The grouping should be customizable.

Proposed technical implementation details (optional)

Originally created by @mlongtin0 on GitHub (Jun 16, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # Description of the new feature/enhancement Large numbers like "16000000" are hard to read in a monitor. Is it 1.6, 16 or 160 millions? I end up trying to select groups of three to make sense of it. I would like to propose to italicize or bold alternating groups, like this: 16<i>000</i>000 or 16<b>000</b>000 This would be enough to make it easier to read. The grouping should be customizable. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 07:03:36 +00:00
claunia commented 2026-01-31 07:03:37 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 16, 2023):

I feel like such an addition might be a little too niche. Is there a reason your application couldn't just format numbers in a more legible way in the first place?

@lhecker commented on GitHub (Jun 16, 2023): I feel like such an addition might be a little too niche. Is there a reason your application couldn't just format numbers in a more legible way in the first place?
claunia commented 2026-01-31 07:03:37 +00:00
Author
Owner
Copy Link

@mlongtin0 commented on GitHub (Jun 16, 2023):

I deal with large numbers all the time, the basic tools don't format, so I end up having to pipe through a number formatter. Even the default Excel is painful that way.

A less niche version would be some sort of regex transform that's applied to the display. It could be used to always put ERROR in bold and red, for example.

@mlongtin0 commented on GitHub (Jun 16, 2023): I deal with large numbers all the time, the basic tools don't format, so I end up having to pipe through a number formatter. Even the default Excel is painful that way. A less niche version would be some sort of regex transform that's applied to the display. It could be used to always put ERROR in bold and red, for example.
claunia commented 2026-01-31 07:03:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 16, 2023):

A less niche version would be some sort of regex transform that's applied to the display. It could be used to always put ERROR in bold and red, for example

Thats in #5916. dunno if the spec I have in progress would adequately cover this tho

@zadjii-msft commented on GitHub (Jun 16, 2023): > A less niche version would be some sort of regex transform that's applied to the display. It could be used to always put ERROR in bold and red, for example Thats in #5916. dunno if the spec I have in progress would adequately cover this tho
claunia commented 2026-01-31 07:03:37 +00:00
Author
Owner
Copy Link

@mlongtin0 commented on GitHub (Jun 16, 2023):

Correct. Duplicate of https://github.com/microsoft/terminal/issues/6297.

@mlongtin0 commented on GitHub (Jun 16, 2023): Correct. Duplicate of https://github.com/microsoft/terminal/issues/6297.
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-Feature 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#20101
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?