Vim: + v and + s split pane not working on VSCode 1.90
Describe the bug
Using <C-w> + v an <C-w> + 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:
- Ensure VSCode is version 1.90
- on a file press
<C-w>followed byvor<C-w>followed bys
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
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 66
- Comments: 28
Commits related to this issue
- fixes #9061 <C-w> + v and <C-w> + s split pane not working on VSCode 1.90 — committed to HenryTSZ/NVim by HenryTSZ 2 years ago
- Fixes #9061 Split pane (`<C-w>v` and `<C-w>s`) not working on VSCode 1.90 (#9072) — committed to s-kai273/Vim by HenryTSZ 2 years ago
Another possible workaround is to modify vim extension settings:
I like it better than modifying
keybinding.jsonbecause it doesn’t break Ctrl+W behaviour in insert mode.At least for vertical/horizontal splits one can one can add the following shortcuts to
keybinding.jsonas a temporary workaround, I guess:here’s that but for config json
I’m having similar issues
<C-w> + v- vertical splitand
<C-w> + s- horizontal splitAre no longer working for me after updating to
1.90.0of visual studio codeWould be nice to have a release for this fix.
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.
In my case, I’m used to using
<C-k>,<C-l>,<C-j>,<C-h.This workaround works in stable /
1.19.0but not in insiders version1.91.0-insider, so there’s probably more changes ahead that will break it again.👍 Cool, add this configuration code snippet to setting.json to bypass the above issue.
Seems like this is due to some changes made for the new “Tab Multi Select” feature
I noticed that
resourceOrContextandcommandContextwereundefinedwhen the action was run viaCommand Palette > Split Editor. When run viaVSCodeVim, they were both empty objects.Setting
workbench.action.splitEditorandworkbench.action.splitEditorOrthogonalaction arguments toundefinedseems 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