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

Split pane is not working #5451

New Issue
Closed
opened 2026-01-31 00:13:42 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 00:13:42 +00:00
Owner
Copy Link

Originally created by @kumarom on GitHub (Dec 7, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.476] Professional Edition
Windows Terminal version (if applicable): Version: 0.7.3382.0

Any other software?

Steps to reproduce

I have two tabs open (1st cmd, 2nd wsl1 Ubuntu) and I wanted to have split pane. So I focused on wsl1 and then pressed ALT + SHIFT + - or ALT + SHIFT + '+'. But there was no change.

Then I closed all tabs. Changed key bindings ALT + SHIFT + - to CTRL + SHIFT + h after editing profiles.json. Reopened all tabs, and then tried CTRL + SHIFT + h. Still no action.

Expected behavior

As per release notes for v0.7.3291.0, it should have split pane.

Actual behavior

Split pane is not working

Originally created by @kumarom on GitHub (Dec 7, 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! --> <!-- 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: Microsoft Windows [Version 10.0.18363.476] Professional Edition Windows Terminal version (if applicable): Version: 0.7.3382.0 Any other software? ``` # Steps to reproduce I have two tabs open (1st cmd, 2nd wsl1 Ubuntu) and I wanted to have split pane. So I focused on wsl1 and then pressed ALT + SHIFT + - or ALT + SHIFT + '+'. But there was no change. Then I closed all tabs. Changed key bindings ALT + SHIFT + - to CTRL + SHIFT + h after editing profiles.json. Reopened all tabs, and then tried CTRL + SHIFT + h. Still no action. # Expected behavior As per release notes for v0.7.3291.0, it should have split pane. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Split pane is not working <!-- What's actually happening? -->
claunia added the Area-SettingsIssue-BugResolution-AnsweredProduct-Terminal labels 2026-01-31 00:13:42 +00:00
claunia commented 2026-01-31 00:13:43 +00:00
Author
Owner
Copy Link

@bluuurgh commented on GitHub (Dec 7, 2019):

For me it only works if I don't use the numpad plus and min keys (which I would prefer) but it does work with the other plus and min keys (near backspace).

@bluuurgh commented on GitHub (Dec 7, 2019): For me it only works if I don't use the numpad plus and min keys (which I would prefer) but it does work with the other plus and min keys (near backspace).
claunia commented 2026-01-31 00:13:44 +00:00
Author
Owner
Copy Link

@Grisu118 commented on GitHub (Dec 9, 2019):

You used the correct key specifier for numbad keys? The following works for me:

            {
                "command": "splitHorizontal",
                "keys": [
                    "alt+shift+numpad_minus"
                ]
            },
            {
                "command": "splitVertical",
                "keys": [
                    "alt+shift+numpad_plus"
                ]
            }

See also here: https://github.com/microsoft/terminal/issues/3856

@Grisu118 commented on GitHub (Dec 9, 2019): You used the correct key specifier for numbad keys? The following works for me: ```json { "command": "splitHorizontal", "keys": [ "alt+shift+numpad_minus" ] }, { "command": "splitVertical", "keys": [ "alt+shift+numpad_plus" ] } ``` See also here: https://github.com/microsoft/terminal/issues/3856
claunia commented 2026-01-31 00:13:44 +00:00
Author
Owner
Copy Link

@kumarom commented on GitHub (Dec 9, 2019):

@Grisu118 Your suggetions work. However, the defaults mentioned in 9145903e11/src/cascadia/TerminalApp/defaults.json (L237-L238) do not. This issue can be closed if the defaults are updated.

@kumarom commented on GitHub (Dec 9, 2019): @Grisu118 Your suggetions work. However, the defaults mentioned in https://github.com/microsoft/terminal/blob/9145903e118bfa3b48749694689aec3a191bc4ac/src/cascadia/TerminalApp/defaults.json#L237-L238 do not. This issue can be closed if the defaults are updated.
claunia commented 2026-01-31 00:13:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2019):

@kumarom This is definitely weird. You're saying that

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

worked for you, but

{
    "command": "splitVertical",
    "keys": [ "ctrl+shift+h" ]
}

didn't? That's really weird. What keyboard layout are you using?

@zadjii-msft commented on GitHub (Dec 9, 2019): @kumarom This is definitely weird. You're saying that ```json { "command": "splitVertical", "keys": [ "alt+shift+numpad_plus" ] } ``` worked for you, but ```json { "command": "splitVertical", "keys": [ "ctrl+shift+h" ] } ``` _didn't_? That's really weird. What keyboard layout are you using?
claunia commented 2026-01-31 00:13:44 +00:00
Author
Owner
Copy Link

@kumarom commented on GitHub (Dec 9, 2019):

@zadjii-msft All I am saying that

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

worked. But { "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] }, does not work and is documented in 9145903e11/src/cascadia/TerminalApp/defaults.json (L237-L238)

@kumarom commented on GitHub (Dec 9, 2019): @zadjii-msft All I am saying that ``` { "command": "splitVertical", "keys": [ "alt+shift+numpad_plus" ] } ``` worked. But `{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] },` does not work and is documented in https://github.com/microsoft/terminal/blob/9145903e118bfa3b48749694689aec3a191bc4ac/src/cascadia/TerminalApp/defaults.json#L237-L238
claunia commented 2026-01-31 00:13:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2019):

@kumarom okay, I think I got confused by your OP where you mentioned that "CTRL + SHIFT + h" didn't work.

What keyboard layout are you using?

Does the alt+shift+plus binding work for you if you use the + key that's not on the numpad? On a QWERTY EN-US keyboard, this is the key with both + and =.

Perhaps we need to update the documentation to be clearer that plus and numpad_plus are not interchangable.

@zadjii-msft commented on GitHub (Dec 9, 2019): @kumarom okay, I think I got confused by your OP where you mentioned that "CTRL + SHIFT + h" didn't work. What keyboard layout are you using? Does the <kbd>alt+shift+plus</kbd> binding work for you if you use the <kbd>+</kbd> key that's _not_ on the numpad? On a QWERTY EN-US keyboard, this is the key with both `+` and `=`. Perhaps we need to update the documentation to be clearer that `plus` and `numpad_plus` are _not_ interchangable.
claunia commented 2026-01-31 00:13:44 +00:00
Author
Owner
Copy Link

@kumarom commented on GitHub (Dec 9, 2019):

@zadjii-msft I tried below and none of them worked for me. I am using QWERTY EN-US keyboard.

  • { "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] },
  • { "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+numpad_plus" ] },
  • { "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift++" ] },
  • { "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+h" ] },
    As per defaults defined here, above should have worked.

Below works:

  • { "command": "splitVertical", "keys": [ "alt+shift+numpad_plus" ] },
  • { "command": "splitVertical", "keys": [ "alt+shift++" ] },
  • { "command": "splitVertical", "keys": [ "alt+shift+plus" ] },
  • { "command": "splitVertical", "keys": [ "alt+shift+h" ] },
@kumarom commented on GitHub (Dec 9, 2019): @zadjii-msft I tried below and none of them worked for me. I am using QWERTY EN-US keyboard. - `{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] },` - `{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+numpad_plus" ] },` - `{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift++" ] },` - `{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+h" ] },` As per defaults defined [here](https://github.com/microsoft/terminal/blob/9145903e118bfa3b48749694689aec3a191bc4ac/src/cascadia/TerminalApp/defaults.json), above should have worked. Below works: - `{ "command": "splitVertical", "keys": [ "alt+shift+numpad_plus" ] },` - `{ "command": "splitVertical", "keys": [ "alt+shift++" ] },` - `{ "command": "splitVertical", "keys": [ "alt+shift+plus" ] },` - `{ "command": "splitVertical", "keys": [ "alt+shift+h" ] },`
claunia commented 2026-01-31 00:13:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2019):

Oh well this is horrifying. That style of keybindings definitely should be working. Lemme dig in a bit...

@zadjii-msft commented on GitHub (Dec 9, 2019): Oh well this is horrifying. That style of keybindings definitely should be working. Lemme dig in a bit...
claunia commented 2026-01-31 00:13:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 9, 2019):

I see what's going on here.

#3722 added support for splitPane, but unfortunately was not included in the 0.7.3382.0 release. So You'll need to keep using splitVertical and splitHorizontal style keybindings until the next update is released.

Sorry for any confusion!

@zadjii-msft commented on GitHub (Dec 9, 2019): I see what's going on here. #3722 added support for `splitPane`, but unfortunately was not included in the 0.7.3382.0 release. So You'll need to keep using `splitVertical` and `splitHorizontal` style keybindings until the next update is released. Sorry for any confusion!
claunia commented 2026-01-31 00:13:45 +00:00
Author
Owner
Copy Link

@andreamaruccia commented on GitHub (Sep 17, 2021):

My personal preference was to confiugre it like this:

  • use the keypads -/+
  • use splitmode so that it will select the current window's shell (if ubuntu it duplicates ubuntu, if powershell it duplicates psh)
  • works on the current version of vscode as opposed of old commands
        {
          "command": {
            "action": "splitPane",
            "split": "horizontal",
            "splitMode": "duplicate"
          },
          "keys": [
            "alt+shift+numpad_minus"
          ]
        },
        {
          "command": {
            "action": "splitPane",
            "split": "vertical",
            "splitMode": "duplicate"
          },
          "keys": [
            "alt+shift+numpad_plus"
          ]
        }
@andreamaruccia commented on GitHub (Sep 17, 2021): My personal preference was to confiugre it like this: * use the keypads -/+ * use splitmode so that it will select the current window's shell (if ubuntu it duplicates ubuntu, if powershell it duplicates psh) * works on the current version of vscode as opposed of old commands ``` { "command": { "action": "splitPane", "split": "horizontal", "splitMode": "duplicate" }, "keys": [ "alt+shift+numpad_minus" ] }, { "command": { "action": "splitPane", "split": "vertical", "splitMode": "duplicate" }, "keys": [ "alt+shift+numpad_plus" ] } ```
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-Bug Product-Terminal 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#5451
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?