starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Font size does not match the settings in default Powershell #9462

New Issue
Closed
opened 2026-01-31 01:55:10 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 01:55:10 +00:00
Owner
Copy Link

Originally created by @kneelesh48 on GitHub (Jul 6, 2020).

Description of the new feature/enhancement

My laptop has a 15.6" 1920px1080p display.
I'm using font Consolas at size 16 in the default PowerShell and that has been the perfect size for my use.

But Windows Terminal font size does not match PowerShell. So I'm using font Consolas at size 11 in WT. Which is a bit bigger than Consolas at size 16 in default PowerShell and size 10 is a little too small.

This is the only reason I keep switching to default PowerShell. Some terminal outputs don't fit like they should in WT on font Consolas at size 11 and size 10 is too small to read. In my specific case, the command is docker ps -a.

Proposed technical implementation details

I propose using the same font sizes as in the default PowerShell. Might be easier to implement than writing a new sizing scheme.

Originally created by @kneelesh48 on GitHub (Jul 6, 2020). # Description of the new feature/enhancement My laptop has a 15.6" 1920px1080p display. I'm using font Consolas at size 16 in the default PowerShell and that has been the perfect size for my use. But Windows Terminal font size does not match PowerShell. So I'm using font Consolas at size 11 in WT. Which is a bit bigger than Consolas at size 16 in default PowerShell and size 10 is a little too small. This is the only reason I keep switching to default PowerShell. Some terminal outputs don't fit like they should in WT on font Consolas at size 11 and size 10 is too small to read. In my specific case, the command is `docker ps -a`. # Proposed technical implementation details I propose using the same font sizes as in the default PowerShell. Might be easier to implement than writing a new sizing scheme.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:55:10 +00:00
claunia commented 2026-01-31 01:55:11 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 6, 2020):

The traditional win32 console host measures fonts in pixel sizes. Unfortunately, we're not going to be changing either system to align with the other. The one the console host used was old and wrong and bad, and the one WT uses is in line with all other applications.
Somebody recently asked for fractional font sizes, so I'm going to close this one out as a /dupe of #6678. That would help with the issue where 10 is too small and 11 is too large.

@DHowett commented on GitHub (Jul 6, 2020): The traditional win32 console host measures fonts in _pixel sizes_. Unfortunately, we're not going to be changing either system to align with the other. The one the console host used was old and wrong and bad, and the one WT uses is in line with all other applications. Somebody recently asked for fractional font sizes, so I'm going to close this one out as a /dupe of #6678. That would help with the issue where 10 is too small and 11 is too large.
claunia commented 2026-01-31 01:55:11 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 6, 2020):

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 (Jul 6, 2020): 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!
claunia commented 2026-01-31 01:55:11 +00:00
Author
Owner
Copy Link

@SharakPL commented on GitHub (Nov 28, 2021):

The traditional win32 console host measures fonts in pixel sizes. Unfortunately, we're not going to be changing either system to align with the other. The one the console host used was old and wrong and bad, and the one WT uses is in line with all other applications. Somebody recently asked for fractional font sizes, so I'm going to close this one out as a /dupe of #6678. That would help with the issue where 10 is too small and 11 is too large.

@DHowett are you sure about that? Looks to me Terminal font size are a lot bigger than they should be. For example here's the Cascadia Mono PL at the same font size on:

Windows Terminal
obraz

Visual Studio Code
obraz

Both apps have the same default zoom level.

@SharakPL commented on GitHub (Nov 28, 2021): > The traditional win32 console host measures fonts in _pixel sizes_. Unfortunately, we're not going to be changing either system to align with the other. The one the console host used was old and wrong and bad, and **the one WT uses is in line with all other applications**. Somebody recently asked for fractional font sizes, so I'm going to close this one out as a /dupe of #6678. That would help with the issue where 10 is too small and 11 is too large. @DHowett are you sure about that? Looks to me Terminal font size are a lot bigger than they should be. For example here's the Cascadia Mono PL at the same font size on: **Windows Terminal** ![obraz](https://user-images.githubusercontent.com/5007456/143778513-b1a564c7-fde6-439f-bf7b-5a4f104ca3da.png) **Visual Studio Code** ![obraz](https://user-images.githubusercontent.com/5007456/143778642-ddb1b519-a83b-4bb3-9ac7-6dab70038cea.png) Both apps have the same default zoom level.
claunia commented 2026-01-31 01:55:11 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 29, 2021):

@SharakPL I am pretty sure 😄

I have overlaid a transparent Terminal window on top of Notepad and Chromium displaying the same font size.

image

image

It appears as though VS Code is the odd one out. Did you specify the font size in points?

@DHowett commented on GitHub (Nov 29, 2021): @SharakPL I am pretty sure :smile: I have overlaid a transparent Terminal window on top of Notepad and Chromium displaying the same font size. ![image](https://user-images.githubusercontent.com/189190/143914675-2dcc76ac-ac00-4f8b-b5cd-c986b8bdf719.png) ![image](https://user-images.githubusercontent.com/189190/143914984-57542897-9e0d-4970-b7eb-52bed49ca472.png) It appears as though _VS Code_ is the odd one out. Did you specify the font size in points?
claunia commented 2026-01-31 01:55:11 +00:00
Author
Owner
Copy Link

@SharakPL commented on GitHub (Nov 29, 2021):

Terminal doesn't specify the unit. I suspect it's in points and that's why it's much bigger. VSCode uses pixels.

@SharakPL commented on GitHub (Nov 29, 2021): Terminal doesn't specify the unit. I suspect it's in points and that's why it's much bigger. VSCode uses pixels.
claunia commented 2026-01-31 01:55:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 29, 2021):

Indeed, that's the central thesis of this issue :)

Terminal specifies font size in points, as do most text editors, terminals, web browsers and IDEs.

The traditional windows console used pixels (really "device independent pixels", which were scaled for the display's scaling factor.)

@DHowett commented on GitHub (Nov 29, 2021): Indeed, that's the central thesis of this issue :) Terminal specifies font size in points, as do most text editors, terminals, web browsers and IDEs. The traditional windows console used pixels (really "device independent pixels", which were scaled for the display's scaling factor.)
claunia commented 2026-01-31 01:55:12 +00:00
Author
Owner
Copy Link

@SharakPL commented on GitHub (Dec 15, 2021):

Terminal specifies font size in points, as do most text editors, terminals, web browsers and IDEs.

Really? I would say points are good only for printers and designs made only to be printed, but for anything else that's supposed to be displayed on the screen (including editors, terminals and especially browsers) pixels should be used.

@SharakPL commented on GitHub (Dec 15, 2021): > Terminal specifies font size in points, as do most text editors, terminals, web browsers and IDEs. Really? I would say points are good only for printers and designs made only to be printed, but for anything else that's supposed to be displayed on the screen (including editors, terminals and [especially browsers](https://css-tricks.com/css-font-size/)) pixels should be used.
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 Resolution-Duplicate
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#9462
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?