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

Pane split vertically is different on non-English keyboard layouts #5234

New Issue
Open
opened 2026-01-31 00:08:16 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:08:16 +00:00
Owner
Copy Link

Originally created by @pellelauritsen on GitHub (Nov 27, 2019).

Originally assigned to: @DHowett on GitHub.

I'm using an English/US Windows 10 Pro 18362 with Danish keyboard layout. And the short cut for pane split vertically is Alt + Shift + "+"

Originally created by @pellelauritsen on GitHub (Nov 27, 2019). Originally assigned to: @DHowett on GitHub. I'm using an English/US Windows 10 Pro 18362 with Danish keyboard layout. And the short cut for pane split vertically is Alt + Shift + "+"
claunia added the Needs-Tag-FixIssue-Docs labels 2026-01-31 00:08:16 +00:00
claunia commented 2026-01-31 00:08:17 +00:00
Author
Owner
Copy Link

@enricoreich commented on GitHub (Nov 27, 2019):

Same here with german/DE keybord layout on a german Windows 10 1909.

@enricoreich commented on GitHub (Nov 27, 2019): Same here with german/DE keybord layout on a german Windows 10 1909.
claunia commented 2026-01-31 00:08:17 +00:00
Author
Owner
Copy Link

@VikingScientist commented on GitHub (Nov 27, 2019):

Norwegian keyboard and I observe the same thing. I assume it is intentional as the = key is already hidden behind a shift modifier. Anyway, I'm mostly happy with the current solution so I only think the documentation needs an update.

My only complaint is that multi-language keyboard setups use shift+alt as the hotkey to change between english and native keyboard layouts. This causes some confusion when combined with the fact that alt+shift is heavily used in pane control. Note that "split vertically" (shift+alt+ '+') does not change layout, but "I think I'm going to add another tab, but on second thought I had a change of heart" (shift+alt), will change your keyboard layout; and consequently move the new pane button to a different place on your keyboard.

@VikingScientist commented on GitHub (Nov 27, 2019): Norwegian keyboard and I observe the same thing. I assume it is intentional as the = key is already hidden behind a shift modifier. Anyway, I'm mostly happy with the current solution so I only think the documentation needs an update. My only complaint is that multi-language keyboard setups [use shift+alt](https://support.office.com/en-us/article/switch-between-languages-using-the-language-bar-1c2242c0-fe15-4bc3-99bc-535de6f4f258) as the hotkey to change between english and native keyboard layouts. This causes some confusion when combined with the fact that alt+shift is heavily used in pane control. Note that "split vertically" (shift+alt+ '+') does *not* change layout, but "I think I'm going to add another tab, but on second thought I had a change of heart" (shift+alt), *will* change your keyboard layout; and consequently move the new pane button to a different place on your keyboard.
claunia commented 2026-01-31 00:08:17 +00:00
Author
Owner
Copy Link

@hanubeki commented on GitHub (Nov 27, 2019):

I saw the line in defaults.json:

{ "command": "splitVertical", "keys": [ "alt+shift+plus" ] },

So I think the release note for v0.7.3291.0 is not correct.

@hanubeki commented on GitHub (Nov 27, 2019): I saw the line in defaults.json: ```json { "command": "splitVertical", "keys": [ "alt+shift+plus" ] }, ``` So I think the release note for v0.7.3291.0 is not correct.
claunia commented 2026-01-31 00:08:18 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 30, 2019):

I assume it is intentional as the = key is already hidden behind a shift modifier.

Yep, that was me simplifying the release notes based on my US-104 keyboard. The true binding is alt+shift+plus, which can be expressed differently depending on your keyboard.

For a US-104 keyboard, alt+plus and alt+shift+= are synonymous with alt+shift+plus. Unfortunately, that doesn't hold for everyone else.

I'm going to file a followup issue for the Shift+Alt thing and close this one out when the release notes get updated.

@DHowett-MSFT commented on GitHub (Nov 30, 2019): >I assume it is intentional as the = key is already hidden behind a shift modifier. Yep, that was me simplifying the release notes based on my US-104 keyboard. The true binding is `alt+shift+plus`, which can be expressed differently depending on your keyboard. For a US-104 keyboard, `alt+plus` and `alt+shift+=` are synonymous with `alt+shift+plus`. Unfortunately, that doesn't hold for everyone else. I'm going to file a followup issue for the <kbd>Shift+Alt</kbd> thing and close this one out when the release notes get updated.
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-Docs Needs-Tag-Fix
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#5234
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?