Hacker News Reader

Comment by koonsolo | Hacker News Reader

I ended up with the best of both worlds (subjective of course!).

I use VSCode with a Vim plugin. I get all the best keystrokes from Vim, and the GUI of VSCode.

For me, going to Vim would be worse, and going to plain VSCode would be worse.

VS Code with a vim plugin is in the uncanny valley of text editors. It doesn't work quite right and a lot of functionality is missing. It's enough that there's more frustration and less productivity for no advantage.

The majority of my movements are moving around files and making minor edits that the vim plugin supports well. It saves me from reaching for the mouse in many case, and that's the entire goal for me.

Works fine for me. Can you give an example?

One thing I have issues with is autocomplete and using . to repeat the last edit (which includes the autocomplete). Other than that, all fine.

Edit: all the vim commands give me a huge advantage on productivity when editing. All the GUI with plugins gives me a huge advantage on project navigation. Would love to see anyone do better using either one or the other.

Try the vscode-neovim[1] plugin instead of the more popular vscode-vim plugin. It runs an actual neovim instance in the background and works so much better than vscode-vim, which I also found was "not quite right" and very laggy. It really is excellent, pretty seamless and can't recommend it enough.

1: https://marketplace.visualstudio.com/items?itemName=asvetlia...

I went the other way, as soon as VSCode-like language server protocol was available for neovim I dropped VSCode. Now I have the same speed with modern features too. In the end it's what's best for you that counts, having quality options helps a lot.

Do you have debugging setup in Vim? (If so, I'd love to hear what that looks like!)

> In the end it's what's best for you that counts, having quality options helps a lot

I agree. I just can't stand the git CLI, and love the GitGraph plugin in VSCode. But like you say everyone has their preferences.

except macros doesnt work! and the multiline editing from vs code doesnt work anymore.

unless you got both to work?

They both work fine for me most of the time.

There are edge cases but I can’t think of a specific right now. When I run into one, which isn’t that often anymore, I’ll open vscode’s terminal panel and do a quick edit in nvim there.

For me I don't use macro's that much. I remeber they worked fine in the Visual Studio plugin, but not sure VSCode. If I really need it for a file, I can always quickly open gvim itself. If you use it in your daily workflow, then it might be an issue indeed. But I don't see a reason why a plugin couldn't offer that (like the Visual Studio plugin).

Vim multiline editing works fine :). Not sure what the VSCode offers thoug (maybe I'm missing out)

Reply on news.ycombinator.com