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

Optionally persist font size changes when changed with CTRL+Mousewheel #4050

New Issue
Open
opened 2026-01-30 23:36:52 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:36:52 +00:00
Owner
Copy Link

Originally created by @naikrovek on GitHub (Sep 25, 2019).

CTRL+MouseWheel font size changes should optionally persist to profiles.json

I move between monitors a lot and this means I change monitor geometries, resolutions, and pixel pitches frequently. Frequently enough that I need to change the font size in Terminal almost daily, and it would be lovely if my font size changes "stick" for the day. The multiple round trips required to change the font size to get it exactly where I want it via profiles.json is a bit tedious. So, for some, and for me definitely, changes to font size should persist when I use CTRL+MouseWheel.

I know this goes against the folks who want this to never persist, so perhaps a new keyboard shortcut is in order, or perhaps the behavior of CTRL+MouseWheel should be exposed in the keybindings section of profiles.json as a command. An additional command could be created (which persists the font size when you zoom) and could then be chosen by those who want this behavior.

Persisting the font size when it is changed with CTRL+MouseWheel is the behavior in Sublime Text and I've gotten quite used to this over time, and now I miss it (I especially miss it in VScode, but that's another issue.)

Thank you.

Originally created by @naikrovek on GitHub (Sep 25, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> # CTRL+MouseWheel font size changes should optionally persist to profiles.json <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> <!-- A clear and concise description of what you want to happen. --> I move between monitors a lot and this means I change monitor geometries, resolutions, and pixel pitches frequently. Frequently enough that I need to change the font size in Terminal almost daily, and it would be lovely if my font size changes "stick" for the day. The multiple round trips required to change the font size to get it exactly where I want it via `profiles.json` is a bit tedious. So, for some, and for me definitely, changes to font size should persist when I use CTRL+MouseWheel. I know this goes against the folks who want this to **never** persist, so perhaps a new keyboard shortcut is in order, or perhaps the behavior of CTRL+MouseWheel should be exposed in the `keybindings` section of `profiles.json` as a `command`. An additional `command` could be created (which persists the font size when you zoom) and could then be chosen by those who want this behavior. Persisting the font size when it is changed with CTRL+MouseWheel is the behavior in Sublime Text and I've gotten quite used to this over time, and now I miss it (I especially miss it in VScode, but that's another issue.) Thank you.
claunia added the Area-SettingsIssue-TaskProduct-Terminal labels 2026-01-30 23:36:52 +00:00
claunia commented 2026-01-30 23:36:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 25, 2019):

So, writing the profiles.json file is tricky business that we're happy to not be doing anymore. Not saying that this isn't possible now, but we'd want to be especially careful, or maybe think of a solution that doesn't involve changing that file.

This sounds to me like a subset of a pair of issues from before:

Though this one seems to have it's own particular path cut out. I'll leave it to the team to decide if it's a dupe or not.

@zadjii-msft commented on GitHub (Sep 25, 2019): So, writing the profiles.json file is tricky business that we're happy to not be doing anymore. Not saying that this isn't possible now, but we'd want to be especially careful, or maybe think of a solution that doesn't involve changing that file. This sounds to me like a subset of a pair of issues from before: * #766 * #1056 Though this one seems to have it's own particular path cut out. I'll leave it to the team to decide if it's a dupe or not.
claunia commented 2026-01-30 23:36:53 +00:00
Author
Owner
Copy Link

@naikrovek commented on GitHub (Sep 25, 2019):

Is there not a settings dialog planned? How will it store settings? Or is it going to use some non-JSON settings store?

To be clear, I am fine if JSON is not involved; I do not care how this is implemented.

@naikrovek commented on GitHub (Sep 25, 2019): Is there not a settings dialog planned? How will it store settings? Or is it going to use some non-JSON settings store? To be clear, I am fine if JSON is not involved; I do not care how this is implemented.
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-Settings Issue-Task Product-Terminal
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#4050
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?