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

ctrl+plus as change font size messes with telnet #18770

New Issue
Closed
opened 2026-01-31 06:23:46 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 06:23:46 +00:00
Owner
Copy Link

Originally created by @michael-r-elp on GitHub (Oct 29, 2022).

Windows Terminal version

1.15.2875.0

Windows build number

10.0.22000.0

Other Software

Microsoft Telnet-Client
10.0.22000.708

Steps to reproduce

With telnet installed and german keyboard layout or any that have ctrl+plus open a telnet session to an host
Try to press ctrl+plus

Change Settings in Windows Terminal and change default keybinding for setting a larger font size to something different than ctrl+plus or delete that keybind entirely and save
Attempt to start another telnet session and try to escape with ctrl+plus

Expected Behavior

Having escape into the telnet prompt work with default windows terminal settings

Actual Behavior

It seems windows terminal has a default keybinding for ctrl+plus, that changes the font size
It might be an better idea to have that as ctrl+numpad_plus or
something that doesn't cause issues when using telnet with the default escape character

My options here were either change or remove the keybinding in windows terminal (I removed it once I found it) or
start a telnet session with -e to specify a custom escape character

Maybe there could be a better default keybinding you could set in windows terminal that would not interfere with telnets default
It would probably also be fine to leave it as is?
But it kinda caused a bit of confusion for me, maybe just having terminal forward ctrl+plus even with a keybinding set for it, might work, but could possibly cause issues in other situations.

I'll leave it up to you guys what you think could/should be done here

Originally created by @michael-r-elp on GitHub (Oct 29, 2022). ### Windows Terminal version 1.15.2875.0 ### Windows build number 10.0.22000.0 ### Other Software Microsoft Telnet-Client 10.0.22000.708 ### Steps to reproduce With telnet installed and german keyboard layout or any that have ctrl+plus open a telnet session to an host Try to press ctrl+plus Change Settings in Windows Terminal and change default keybinding for setting a larger font size to something different than ctrl+plus or delete that keybind entirely and save Attempt to start another telnet session and try to escape with ctrl+plus ### Expected Behavior Having escape into the telnet prompt work with default windows terminal settings ### Actual Behavior It seems windows terminal has a default keybinding for ctrl+plus, that changes the font size It might be an better idea to have that as ctrl+numpad_plus or something that doesn't cause issues when using telnet with the default escape character My options here were either change or remove the keybinding in windows terminal (I removed it once I found it) or start a telnet session with `-e` to specify a custom escape character Maybe there could be a better default keybinding you could set in windows terminal that would not interfere with telnets default It would probably also be fine to leave it as is? But it kinda caused a bit of confusion for me, maybe just having terminal forward ctrl+plus even with a keybinding set for it, might work, but could possibly cause issues in other situations. I'll leave it up to you guys what you think could/should be done here
claunia added the Issue-QuestionNeeds-TriageIssue-BugResolution-Answered labels 2026-01-31 06:23:46 +00:00
claunia commented 2026-01-31 06:23:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 31, 2022):

It looks like we've got it bound to both:

8ea3cb9972/src/cascadia/TerminalSettingsModel/defaults.json (L444-L447)

I honestly think the best recommendation here is just to unbind ctrl+plus if you're already using it for something in your client app (telnet).

But thanks for bringing this up! I honestly didn't know ctrl+plus was used for that in telnet!

@zadjii-msft commented on GitHub (Oct 31, 2022): It looks like we've got it bound to both: https://github.com/microsoft/terminal/blob/8ea3cb9972491dec322f53ad69525a431a1d8431/src/cascadia/TerminalSettingsModel/defaults.json#L444-L447 I honestly think the best recommendation here is just to unbind `ctrl+plus` if you're already using it for something in your client app (telnet). But thanks for bringing this up! I honestly didn't know `ctrl+plus` was used for that in telnet!
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-Bug 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#18770
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?