<C-w> + v and <C-w> + s split pane not working on VSCode 1.90

[ljones140]

Describe the bug

Using <C-w> + v an + s` for new panes are no longer working when on latest version of VSCode 1.90 https://code.visualstudio.com/updates/v1_90

To Reproduce Steps to reproduce the behavior:

1. Ensure VSCode is version 1.90
2. on a file press <C-w> followed by v or <C-w> followed by s

Expected behavior New pane opens

Environment (please complete the following information):

• Extension (VsCodeVim) version: 1.27.3
• VSCode version: 1.90
• OS: Mac 14.5

[ljones140]

Downgrading to VSCode 1.89.1 and split panes works

[levidavidmurray]

I didn't realize my VSCode updated and thought I was going crazy when <C-w> + v wasn't working. Hopefully we can get a quick resolution for this

[levidavidmurray]

Seems like this is due to some changes made for the new "Tab Multi Select" feature

I noticed that resourceOrContext and commandContext were undefined when the action was run via Command Palette > Split Editor. When run via VSCodeVim, they were both empty objects.

Setting workbench.action.splitEditor and workbench.action.splitEditorOrthogonal action arguments to undefined seems to fix the immediate issue. But, I don't know enough about the architecture of VSCodeVim nor VSCode to say if this is the correct solution.

https://github.com/VSCodeVim/Vim/assets/46084870/12f4294f-b23f-42a5-9797-7cf1313b3cff

[sasacocic]

I'm having similar issues

<C-w> + v- vertical split

and

<C-w> + s - horizontal split

Are no longer working for me after updating to 1.90.0 of visual studio code

[david-xorcon]

Same here - broken since 1.90.0

[Yin-SHT]

Same here

[ljones140]

I'm having similar issues

<C-w> + v- vertical split

and

<C-w> + s - horizontal split

Are no longer working for me after updating to 1.90.0 of visual studio code

I'll edit the issue to add these thanks

[kianryan]

This wasn't broken on insiders until the latest update. Now broken on 1.91.0-insider - same behaviour

[viddo]

At least for vertical/horizontal splits one can one can add the following shortcuts to keybinding.json as a temporary workaround, I guess:

    {
        "key": "ctrl+w v",
        "command": "workbench.action.splitEditor"
    },
    {
        "key": "ctrl+w s",
        "command": "workbench.action.splitEditorDown"
    },

[dim-an]

Another possible workaround is to modify vim extension settings:

{
    ...
    "vim.normalModeKeyBindings": [
        {
            "before": ["C-w", "v"],
            "after": [":", "v", "s", "<Enter>"],
        },
        {
            "before": ["C-w", "s"],
            "after": [":", "s", "p", "<Enter>"],
        },
    ...
}

I like it better than modifying keybinding.json because it doesn't break Ctrl+W behaviour in insert mode.

[basictheprogram]

Adding same behavior for menu options

• View > Editor Layout > Split Down
• View > Editor Layout > Split Up

[jayhanjaelee]

Same Here

[viddo]

Another possible workaround is to modify vim extension settings:

{
    ...
    "vim.normalModeKeyBindings": [
        {
            "before": ["C-w", "v"],
            "after": [":", "v", "s", "<Enter>"],
        },
        {
            "before": ["C-w", "s"],
            "after": [":", "s", "p", "<Enter>"],
        },
    ...
}

I like it better than modifying keybinding.json because it doesn't break Ctrl+W behaviour in insert mode.

This workaround works in stable / 1.19.0 but not in insiders version 1.91.0-insider, so there's probably more changes ahead that will break it again.

[aurum77]

At least for vertical/horizontal splits one can one can add the following shortcuts to keybinding.json as a temporary workaround, I guess:

    {
        "key": "ctrl+w v",
        "command": "workbench.action.splitEditor"
    },
    {
        "key": "ctrl+w s",
        "command": "workbench.action.splitEditorDown"
    },

here's that but for config json

"vim.normalModeKeyBindings": [
    {
      "before": [
        "<C-w>",
        "v"
      ],
      "commands": [
        "workbench.action.splitEditor"
      ]
    },
    {
      "before": [
        "<C-w>",
        "s"
      ],
      "commands": [
        "workbench.action.splitEditorDown"
      ]
    },
]

[guunergooner]

At least for vertical/horizontal splits one can one can add the following shortcuts to keybinding.json as a temporary workaround, I guess:

    {
        "key": "ctrl+w v",
        "command": "workbench.action.splitEditor"
    },
    {
        "key": "ctrl+w s",
        "command": "workbench.action.splitEditorDown"
    },

here's that but for config json

"vim.normalModeKeyBindings": [
    {
      "before": [
        "<C-w>",
        "v"
      ],
      "commands": [
        "workbench.action.splitEditor"
      ]
    },
    {
      "before": [
        "<C-w>",
        "s"
      ],
      "commands": [
        "workbench.action.splitEditorDown"
      ]
    },
]

👍 Cool, add this configuration code snippet to setting.json to bypass the above issue.

[cochranjdlz]

For anyone interested, I was able to additionally add the following config to allow me to regain my keyboard navigation, which also broke when I updated.

  {
    "key": "ctrl+w k",
    "command": "workbench.action.navigateUp"
  },
  {
    "key": "ctrl+w j",
    "command": "workbench.action.navigateDown"
  },
  {
    "key": "ctrl+w h",
    "command": "workbench.action.navigateLeft"
  },
  {
    "key": "ctrl+w l",
    "command": "workbench.action.navigateRight"
  },

In my case, I'm used to using <C-k>, <C-l>, <C-j>, <C-h.

[junhan-z]

Same here.

Also I think ctrl+w o (show current panel and close others) and ctrl+w q (close current panel) are also broken.

[fivetran-danandreiganea]

Same here

[CWEzio]

Same problem

[jakyns]

when will this fix?

[jirol9xa]

same

[laipz8200]

Same here

[basictheprogram]

Still have the problem in 1.90.2 on macOS

[KuanYuLai]

same

[jakyns]

how can we push this to fix as soon as possible?

[cloone8]

Same problem here! Would be great to have this fixed instead of having to use a workaround. Wish I could do this myself, but I haven't got the time to dive into a new open source project atm.

[bluddy]

Would be nice to have a release for this fix.

[KholdStare]

@J-Fields Can this fix be released? I still need to keep resetting VSCode to an older version. Thank you!