hylobates@jlai.lu to linuxmemes@lemmy.worldEnglish · 21 hours agoDon’t get me wrong…jlai.luimagemessage-square87fedilinkarrow-up1458arrow-down124
arrow-up1434arrow-down1imageDon’t get me wrong…jlai.luhylobates@jlai.lu to linuxmemes@lemmy.worldEnglish · 21 hours agomessage-square87fedilink
minus-squareBysmuthlinkfedilinkEnglisharrow-up7arrow-down1·18 hours agoCode and intellij have plugins available to use vim keybindings on them. I like this approach to get the best of both worlds
minus-squarelime!@feddit.nulinkfedilinkEnglisharrow-up9·17 hours agothe vim plugins are so bad… they only support the super basic stuff, as soon as you want flags with your search or chaining of commands they are useless
minus-squareSomething Burger 🍔@jlai.lulinkfedilinkarrow-up9·edit-217 hours agoThe neovim plugin for VSCode uses the actual nvim binary as a backend and supports all features.
minus-squareCosmicTurtle0@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up8·18 hours agoIt’s not the same. Granted it’s been years since I used the vim plugin but last time I tried it couldn’t even do standard find and replace.
Code and intellij have plugins available to use vim keybindings on them. I like this approach to get the best of both worlds
the vim plugins are so bad… they only support the super basic stuff, as soon as you want flags with your search or chaining of commands they are useless
The neovim plugin for VSCode uses the actual nvim binary as a backend and supports all features.
that’s a pretty neat solution
This is the way
It’s not the same. Granted it’s been years since I used the vim plugin but last time I tried it couldn’t even do standard find and replace.