A question for the people who use vim keybindings in IDEs: how do you deal with keybindings for IDE tasks which are not part of vim (like using the debugger, refactoring, code completion, etc.)? The last time I tried to use vim bindings in an IDE there were quite some overlaps with these so I found myself coming up with compromise systems which didn’t work that well because they weren’t coherent.
At least for PyCharm, this was somewhat easier on macOS than on Windows, since you have control, option, command and shift, instead of just Ctrl, Alt, and Shift (well, and the Win key, but the OS reserves too many bindings there.) On macOS, The IDE uses command for most things, while Vim usually uses control when it needs a modifier at all. On Windows they both want to use Ctrl, so it’s more difficult to configure all the bindings.
Some IDEs are just very accommodating about this, e.g. PyCharm. So that’s great.
Some of them aren’t, like VS Code. For those, I just manually reconfigure the clashing key bindings. It’s annoying, but it only takes ~15 minutes total.
Thanks for your answer. Part of the problem might have been that I wasn’t that proficient with vim. When I reconfigured the clashing key bindings of the IDE I sometimes unknowingly overwrote a vim command which turned out to be useful later on. So I had to reconfigure numerous times which annoyed me so much that I abandoned the approach at the time.
A question for the people who use vim keybindings in IDEs: how do you deal with keybindings for IDE tasks which are not part of vim (like using the debugger, refactoring, code completion, etc.)? The last time I tried to use vim bindings in an IDE there were quite some overlaps with these so I found myself coming up with compromise systems which didn’t work that well because they weren’t coherent.
At least for PyCharm, this was somewhat easier on macOS than on Windows, since you have
control
,option
,command
andshift
, instead of justCtrl
,Alt
, andShift
(well, and theWin
key, but the OS reserves too many bindings there.) On macOS, The IDE usescommand
for most things, while Vim usually usescontrol
when it needs a modifier at all. On Windows they both want to useCtrl
, so it’s more difficult to configure all the bindings.Some IDEs are just very accommodating about this, e.g. PyCharm. So that’s great.
Some of them aren’t, like VS Code. For those, I just manually reconfigure the clashing key bindings. It’s annoying, but it only takes ~15 minutes total.
Thanks for your answer. Part of the problem might have been that I wasn’t that proficient with vim. When I reconfigured the clashing key bindings of the IDE I sometimes unknowingly overwrote a vim command which turned out to be useful later on. So I had to reconfigure numerous times which annoyed me so much that I abandoned the approach at the time.