Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split pane is not working #3877

Closed
kumarom opened this issue Dec 7, 2019 · 10 comments
Closed

Split pane is not working #3877

kumarom opened this issue Dec 7, 2019 · 10 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered

Comments

@kumarom
Copy link

kumarom commented 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

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 7, 2019
@bluuurgh
Copy link

bluuurgh commented 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).

@Grisu118
Copy link

Grisu118 commented 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: #3856

@kumarom
Copy link
Author

kumarom commented Dec 9, 2019

@Grisu118 Your suggetions work. However, the defaults mentioned in

{ "command": { "action": "splitPane", "split": "horizontal"}, "keys": [ "alt+shift+-" ] },
{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] },
do not. This issue can be closed if the defaults are updated.

@zadjii-msft
Copy link
Member

@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 zadjii-msft added Area-Settings Issues related to settings and customizability, for console or terminal Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Dec 9, 2019
@kumarom
Copy link
Author

kumarom commented 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

{ "command": { "action": "splitPane", "split": "horizontal"}, "keys": [ "alt+shift+-" ] },
{ "command": { "action": "splitPane", "split": "vertical"}, "keys": [ "alt+shift+plus" ] },

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Dec 9, 2019
@zadjii-msft
Copy link
Member

@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 zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Dec 9, 2019
@kumarom
Copy link
Author

kumarom commented 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" ] },

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Dec 9, 2019
@zadjii-msft
Copy link
Member

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

@zadjii-msft zadjii-msft self-assigned this Dec 9, 2019
@DHowett-MSFT DHowett-MSFT added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Dec 9, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Dec 9, 2019
@DHowett-MSFT DHowett-MSFT removed the Needs-Attention The core contributors need to come back around and look at this ASAP. label Dec 9, 2019
@DHowett-MSFT DHowett-MSFT added this to the Terminal v1.0 milestone Dec 9, 2019
@zadjii-msft
Copy link
Member

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!

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Dec 9, 2019
@zadjii-msft zadjii-msft removed this from the Terminal v1.0 milestone Dec 9, 2019
@zadjii-msft zadjii-msft added the Resolution-Answered Related to questions that have been answered label Dec 9, 2019
@zadjii-msft zadjii-msft removed their assignment Dec 9, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Dec 9, 2019
@andreamaruccia
Copy link

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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

6 participants