Default mappings for gI: goToImplementation instead enters insert mode at start of line

[klaskow]

Is your feature request related to a problem? Please describe.

The current default keybinding for gI ("enters insert mode at start of line") prioritizes a niche Vim command over goToImplementation, a fundamental code navigation feature used by a much larger majority of developers.

Describe the solution you'd like

The goToImplementation command should be treated as a primary feature with a better default shortcut. I suggest assigning it to gI. For inspiration on sensible defaults that cater to a modern developer workflow, I recommend looking at highly popular Neovim distributions like LazyVim.

Describe alternatives you've considered

A setting could be introduced in settings.json, such as "vim.mappingsMode": "IDE" (default) or "vim.mappingsMode": "vim", to let users choose their preferred keybinding philosophy. While I know it's easy to create custom mappings, I believe the default configuration should be more sensible out-of-the-box for both general developers and existing Vim users.

Additional context

The goToImplementation command is a cornerstone of modern software development for navigating any non-trivial codebase. The existing gI functionality can be easily replicated in Vim by simply using 0i. This makes gI an ideal and available candidate for a goToImplementation mapping, providing a better out-of-the-box experience for most users.

---

Here's the PR. Mappings works, but the tests are failing. The old tests need to be fixed, and new ones are needed for the gI mapping.

[mikaelmedina]

The vim default for gI is to do what it does in this extension, and thus the sensible default is for it to keep behaving like that.
https://vimhelp.org/insert.txt.html#gI

Your second alternative would be a more viable solution to the issue, to have a suite of configs with different keybindings, but you can't cater to all the bindings every user expects, so we're back to square one. Settings.json with custom keybindings is the way to go

[klaskow]

Okay, I forgot about the [count] for gI, so in that case, 0i is indeed not an alternative.

How about we introduce <Leader> KEY mappings for the LSP and the debugger? This would avoid conflicts and provide some sensible default settings for developers right after installing the plugin. I know you can't please everyone, but if you look at a few Vim/Neovim distributions, you'll notice that the LSP and debugger usually have similar keybindings. So, if we prefix these keys with <Leader>, the plugin could support these shortcuts out of the box.

For example, I have a few VSCode profiles, and each one requires additional Vim configuration after installing a plugin.

We face a similar situation when, for example, reviewing a pull request in the browser-based VSCode. You could install the plugin and navigate the code using the default keybindings at the same time.