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

Keybinding for increasing fontSize (Swedish Keyboard layout) #10302

New Issue
Closed
opened 2026-01-31 02:17:49 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:17:49 +00:00
Owner
Copy Link

Originally created by @einarpersson on GitHub (Aug 26, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2233.0

Any other software? No.

Steps to reproduce

Note: This bug applies to Swedish Keyboard Layout.
Fresh install of Windows Terminal

can decrease fontSize by pressing ctrl AND -
cannot increase fontSize by pressing ctrl AND +
(note: the keybindings above is "default" in other apps, including Google Chrome and VS Code)

Notice that the default keybinding (reached by alt-clicking on settings) for increase fontSize is ctrl+=. The = is a key that does not exist on my Swedish Keyboard. I have a + instead.

Open settings.json in order to change keybindings.

cannot change the keybinding for increasing the fontSize from ctrl+= to ctrl++ (it is marked as an error).

Expected behavior

  1. I expect that the default keybindings for increasing / decreasing fontSize "just works" for my Swedish Keyboard layout, just as it does in VSCode

  2. I expect it to be possible to make keybindings to the +-key which I have on my keyboard.

Actual behavior

See above.

Originally created by @einarpersson on GitHub (Aug 26, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.1.2233.0 Any other software? No. ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Note: This bug applies to **Swedish Keyboard Layout**. Fresh install of Windows Terminal **can** decrease fontSize by pressing `ctrl AND -` **cannot** increase fontSize by pressing `ctrl AND +` (note: the keybindings above is "default" in other apps, including Google Chrome and VS Code) Notice that the default keybinding (reached by alt-clicking on settings) for increase fontSize is `ctrl+=`. The `=` is a key that does not exist on my Swedish Keyboard. I have a `+` instead. Open `settings.json` in order to change keybindings. **cannot** change the keybinding for increasing the fontSize from `ctrl+=` to `ctrl++` (it is marked as an error). # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> 1. I expect that the default keybindings for increasing / decreasing fontSize "just works" for my Swedish Keyboard layout, just as it does in VSCode 2. I expect it to be possible to make keybindings to the `+`-key which I have on my keyboard. # Actual behavior <!-- What's actually happening? --> See above.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 02:17:49 +00:00
claunia commented 2026-01-31 02:17:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 26, 2020):

I'm not sure how different the Swedish and German keyboard layouts are, but maybe #3788 might be useful?

(as a matter of linking related threads, #3737 looks related as well)

@zadjii-msft commented on GitHub (Aug 26, 2020): I'm not sure how different the Swedish and German keyboard layouts are, but maybe #3788 might be useful? (as a matter of linking related threads, #3737 looks related as well)
claunia commented 2026-01-31 02:17:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 30, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 30, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 02:17:51 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Sep 1, 2020):

Oh, if you want to represent Ctrl++ as a keybinding, write it as ctrl+plus. We use '+' as a separator so that's why you were getting the error.

@carlos-zamora commented on GitHub (Sep 1, 2020): Oh, if you want to represent <kbd>Ctrl</kbd>+<kbd>+</kbd> as a keybinding, write it as `ctrl+plus`. We use '+' as a separator so that's why you were getting the error.
claunia commented 2026-01-31 02:17:51 +00:00
Author
Owner
Copy Link

@einarpersson commented on GitHub (Sep 2, 2020):

Oh, if you want to represent Ctrl++ as a keybinding, write it as ctrl+plus. We use '+' as a separator so that's why you were getting the error.

@carlos-zamora That solved it! Thanks! I wonder however how you could help all these people with different keyboard layouts who expect this keybinding to work out of the box (once again: as it works in VSCode, Google Chrome, etc.).

I'm closing this now since I'm happy

@einarpersson commented on GitHub (Sep 2, 2020): > Oh, if you want to represent Ctrl++ as a keybinding, write it as `ctrl+plus`. We use '+' as a separator so that's why you were getting the error. @carlos-zamora That solved it! Thanks! I wonder however how you could help all these people with different keyboard layouts who expect this keybinding to work out of the box (once again: as it works in VSCode, Google Chrome, etc.). I'm closing this now since I'm happy
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-Attention 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#10302
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?