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

font size setting doesn't affect all apps #18870

New Issue
Closed
opened 2026-01-31 06:26:45 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:26:45 +00:00
Owner
Copy Link

Originally created by @gyorokpeter on GitHub (Nov 11, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22621.819

Other Software

N/A

Steps to reproduce

Go to settings -> Command Prompt -> Appearance, change Font size e.g. to 10 (from the default of 12)
Launch various console apps

Expected Behavior

The font size setting should apply to all apps.

Actual Behavior

The font size setting is selectively applied to various apps, with no way to change it for the apps where it doesn't work.
One thing that might be relevant that in apps where it doesn't work, the tab icon looks like a box showing C:\ on a white background, while in apps where it does, the icon has C:\_ (there is an extra underscore) and on a black background.

Originally created by @gyorokpeter on GitHub (Nov 11, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22621.819 ### Other Software N/A ### Steps to reproduce Go to settings -> Command Prompt -> Appearance, change Font size e.g. to 10 (from the default of 12) Launch various console apps ### Expected Behavior The font size setting should apply to *all* apps. ### Actual Behavior The font size setting is selectively applied to various apps, with no way to change it for the apps where it doesn't work. One thing that might be relevant that in apps where it doesn't work, the tab icon looks like a box showing `C:\` on a white background, while in apps where it does, the icon has `C:\_` (there is an extra underscore) and on a _black_ background.
claunia added the Issue-QuestionNeeds-TriageResolution-AnsweredArea-DefApp labels 2026-01-31 06:26:46 +00:00
claunia commented 2026-01-31 06:26:47 +00:00
Author
Owner
Copy Link

@gyorokpeter commented on GitHub (Nov 11, 2022):

Further experimentation reveals that the reason the font size setting doesn't work in all apps is that some are launched using the "Command Prompt" profile, while others are launched using the "Default" profile. Changing both is a workaround for now, but it still leaves open the question why there is a discrepancy in which profile is used.
It seems that "Command Prompt" gets used for batch files and "Default" for binaries. For me there is little functional difference between the two - I launch them from shortcuts anyway, and I try to make shortcuts with enough command line parameters if possible, and switch to using a batch file when that stops being enough, e.g. if changing PATH is necessary. However then it's still the same app, it just has a wrapper script around it, so from the user perspective it makes little sense to use a different profile for the two.

@gyorokpeter commented on GitHub (Nov 11, 2022): Further experimentation reveals that the reason the font size setting doesn't work in all apps is that some are launched using the "Command Prompt" profile, while others are launched using the "Default" profile. Changing both is a workaround for now, but it still leaves open the question why there is a discrepancy in which profile is used. It seems that "Command Prompt" gets used for batch files and "Default" for binaries. For me there is little functional difference between the two - I launch them from shortcuts anyway, and I try to make shortcuts with enough command line parameters if possible, and switch to using a batch file when that stops being enough, e.g. if changing PATH is necessary. However then it's still the same app, it just has a wrapper script around it, so from the user perspective it makes little sense to use a different profile for the two.
claunia commented 2026-01-31 06:26:47 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Nov 11, 2022):

I could not reproduce this issue on the latest Preview

https://user-images.githubusercontent.com/78153320/201370857-5ea008c7-afd3-4a36-8439-45814073f236.mp4

@237dmitry commented on GitHub (Nov 11, 2022): I could not reproduce this issue on the latest `Preview` https://user-images.githubusercontent.com/78153320/201370857-5ea008c7-afd3-4a36-8439-45814073f236.mp4
claunia commented 2026-01-31 06:26:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 11, 2022):

Yea, this is also by design. The Terminal attempts to "match" the commandline application to one of your existing profiles, when determining what settings to use. If it can't find a match, then it'll just use the "defaults" profile for that application's settings.

When you change the settings for "Command Prompt", it's only going to change the settings for cmd.exe launches.

@zadjii-msft commented on GitHub (Nov 11, 2022): Yea, this is also by design. The Terminal attempts to "match" the commandline application to one of your existing profiles, when determining what settings to use. If it can't find a match, then it'll just use the "defaults" profile for that application's settings. When you change the settings for "Command Prompt", it's only going to change the settings for `cmd.exe` launches.
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 Area-DefApp Issue-Question Needs-Triage 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#18870
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?