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

Ctrl+= does not increase font size by default, need to set keybinding in settings.json for it to work #10993

New Issue
Closed
opened 2026-01-31 02:35:40 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 02:35:40 +00:00
Owner
Copy Link

Originally created by @corneliusroemer on GitHub (Oct 12, 2020).

Environment

Windows build number: 10.0.18363.0 Microsoft Windows NT
Windows Terminal version (if applicable): Windows Terminal (Unpackaged) Version: 1.2.200825001-release1.2

Steps to reproduce

Try to increase font size by pressing <C>+=

Expected behavior

Font size increases

Actual behavior

Font size does not increase

Additional observations

  • Font size decrease with <C>+- works. So does reset with <C>+0
  • Manually mapping <C>+= to increase font in settings.json works as a workaround - but it shouldn't be necessary, this should be default setting. This is what made it work: { "command": { "action": "adjustFontSize", "delta": 1 }, "keys": "ctrl+=" }
Originally created by @corneliusroemer on GitHub (Oct 12, 2020). # Environment ```none Windows build number: 10.0.18363.0 Microsoft Windows NT Windows Terminal version (if applicable): Windows Terminal (Unpackaged) Version: 1.2.200825001-release1.2 ``` # Steps to reproduce Try to increase font size by pressing `<C>+=` # Expected behavior Font size increases # Actual behavior Font size does not increase # Additional observations - Font size decrease with `<C>+-` works. So does reset with `<C>+0` - Manually mapping `<C>+=` to increase font in `settings.json` works as a workaround - but it shouldn't be necessary, this should be default setting. This is what made it work: { "command": { "action": "adjustFontSize", "delta": 1 }, "keys": "ctrl+=" }
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 02:35:40 +00:00
claunia commented 2026-01-31 02:35:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 12, 2020):

Windows Terminal version (if applicable): Windows Terminal (Unpackaged) Version: 1.2.200825001-release1.2

First, you're using a version of Terminal that's a couple months out of date (and you're using it in an unexpected/unusual configuration (Unpackaged)).

Puzzlingly, this binding is in the default set. I wonder what's up.

@DHowett commented on GitHub (Oct 12, 2020): > ``` > Windows Terminal version (if applicable): Windows Terminal (Unpackaged) Version: 1.2.200825001-release1.2 > ``` First, you're using a version of Terminal that's a couple months out of date (and you're using it in an unexpected/unusual configuration (Unpackaged)). Puzzlingly, this binding _is_ in the default set. I wonder what's up.
claunia commented 2026-01-31 02:35:41 +00:00
Author
Owner
Copy Link

@corneliusroemer commented on GitHub (Oct 12, 2020):

TL;DR: When upgrading to v1.3 and installing by way of .msixbundle as opposed to rename/unzip/repeat it works by default.

I'm happy to explain what the original setup was nonetheless.

There was an AppLocker issue, so I installed by manually unzipping as you explained here: https://github.com/microsoft/terminal/issues/6046. That's why it's Unpackaged.

I don't know why I installed the old version, that just happened so, I guess. BUT, thanks for pointing it out, I now tried installing the new .msixbundle v1.3 and tada now AppLocker no longer complained and the problem is solved.

@corneliusroemer commented on GitHub (Oct 12, 2020): TL;DR: When upgrading to v1.3 and installing by way of `.msixbundle` as opposed to rename/unzip/repeat it works by default. I'm happy to explain what the original setup was nonetheless. There was an AppLocker issue, so I installed by manually unzipping as you explained here: https://github.com/microsoft/terminal/issues/6046. That's why it's `Unpackaged`. I don't know why I installed the old version, that just happened so, I guess. BUT, thanks for pointing it out, I now tried installing the new `.msixbundle` v1.3 and tada now AppLocker no longer complained and the problem is solved.
claunia commented 2026-01-31 02:35:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 12, 2020):

Happy to hear it! 😄

@DHowett commented on GitHub (Oct 12, 2020): Happy to hear it! :smile:
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 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#10993
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?