Found the answer, this is not calva specific. https://github.com/VSCodeVim/Vim/blob/master/README.md#mac-setup

What does it mean to tap the navigation keys?

Probably HJKL, and so on. Without proper setup on macOS you have to lift and press the keys over and over to keep moving. In normal vim usage you can just press and hold a movement key to keep moving.

correct @U44S24V16

Seems to be ok in Cave Man mode.

I think adding this to the backspace keybinding's when rule makes things work for me personally. I'm not sure what you'd do in the extension to fix it. && vim.mode == 'Insert'

The docs have a page for Vim. Care to submit a PR that explains your findings?

I think Vim extensions are too different from normal VS Code behavior to reasonably expect much in the way of official support from Calva. Much of Calva's functionally is exposed as an API to other extensions. It would be awesome if someone committed to making a Vim-Calva extension that used that to bridge the two worlds.

That’s interesting ^

@U09A987EV please file an issue about that problem.

Done, thanks https://github.com/BetterThanTomorrow/calva/issues/2019

Thanks!

Unfortunately the Calva extension API is covering only a tiny sliver of Calva so I doubt anyone can use it to create a VIM-friendly version. OTOH, it seems to work pretty ok from what I hear from users. OTOH2 I hadn't heard f this search prompt problem before... Maybe people just add that to their when clause and feel done with it. I would pull a PR fixing the when clause in Calva's default binding, btw.

If nothing else, a Vim-specific extension provides installable defaults that can be maintained by someone who actually uses Vim mode. Beyond that, supporting an extension maintainer (again, who actually uses Vim mode), by exposing whatever they need exposed in the API, is way more realistic than trying to guess at what might give that select group of users a pleasant and coherent experience.

Similar to how the Nrepl team "supports" Calva users, but is not generally expected to deal with VS Code specific issues directly.

Yes it makes sense. There is a Calva team for the nrepl team to support, though. There are a lot of abandoned extensions, and that can cause more troubles for users. I wonder if an extension can provide defaults for other extensions? Then it might be worth it that we release a VIM Calva with mostly that and maintain it in the team.

Actually, that sounds promising. A good set of default keybindings would be a useful enough feature-set for initial release. The first-draft can be as simple as writing directly to keybindings.json, instead of worrying about cross-talk between extensions. Then move over any existing tweaks that are only there to support Vim, (such as the proposed fix for the OP of this thread). That would provide a place to focus on potential Vim mode features, without undue interference with the base project. Might even be inspiration enough to draw in a dedicated maintainer, with a real interest in building useful features. 🤞 If not, at least Calva has control, to ensure maintenance continuity if it proves useful, or to swallow/deprecate it otherwise. Worst case, I think it gives as opportunity to experiment on what features Calva needs to provide for exposing an API to be useful for other extensions.