81–90 of 112 posts
This seems like a lot of work to ultimately have a Frankenstein monster. Just use NeoVim. Name one reason why you need VSCode.
You might be able to convince me that for certain languages and tasks, a Jetbrains editor is better than using a plugged up Vim or Emacs. And the up front cost is well known, and their corporate model is easy to understand. You’ll never convince me, however, that Microsoft’s embrace, extend, extinguish partially proprietary editor that uses the same LSPs as any other LSP client should be used by anyone. I wouldn’t to…
VSCode's multiple cursors is generally more powerful than Vim's nasty small imperative commands you have to glue together to try to get efficient editing.
I reverted to Vim after trying NeoVim for a few weeks simply because a lot of Vim defaults had to be chased-down and configured just to get basic Vim features in NeoVim. NeoVim also requires messing with a ton of config files compared with Vim so no thanks.
Hmm, I used vim for nearly a decade then switched to neovim a few years ago and it was pretty much seamless. I've only got one config file for neovim that still works for vim, so your info on that is just plain wrong. What defaults did you have difficulty with? All my settings were mostly the same.
Same.
Neovim just enables most of the settings almost all Vim users turn on anyway; it’s not a dramatic change by any means.
This seems like a lot of work to ultimately have a Frankenstein monster. Just use NeoVim. Name one reason why you need VSCode.
I don't have to spend a bunch of time configuring VSCode, I can simply do a one-click install for plugins, and I can focus on the editing interface with Neovim.
AstroNvim comes to mind https://github.com/AstroNvim/AstroNvim
Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
Exactly, most python plugins like black, code formatters, auto complete etc don't even work with these plugins.
Earlier quoted context omitted.
perhaps onivim would be a good VSCode alternative for you, I think they have a mode like the browser vim extensions that labels everything on screen with a key you can press instead of clicking. https://onivim.io/
Onivim development has stopped, it is now abandonware: https://github.com/onivim/oni2/issues/3811#issuecomment-9103...
Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
I do now have memorized some mix of vim and vscode keybindings, but to me it's worth it. I'm not at 100% keyboard navigation because in some cases I've burned 5-10 minutes looking up a shortcut, repeatedly 1/mo for 3 months. After so many (overly) spaced repetitions, I recognize the shortcut isn't worth memorizing. > Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems…
Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
I used to use this before I switched away from VSCode for greener pastures. It was far and away the best option for vim editing. It’s great because you can still make use of any neovim plugins you have without needing extra VSCode extensions.
What are your greener pastures?
I was a big vim user back before VSCode, so I’m happy being back in my obscure editor hole.