5 ms·
I've been using Vim more and more in the past few months, but I still use VS Code primarily for a lot of my work. At work, I do a lot of Node/TS stuff, so VS Co
by jjice 6y ago
I've been using Vim more and more in the past few months, but I still use VS Code primarily for a lot of my work. At work, I do a lot of Node/TS stuff, so VS Code just offers a whole wealth of tools that I'm already familiar with. I'm sure I could pimp out Vim to do it just as well, if not better, but I still enjoy VS Code.
Where Vim shines for me is for creating and editing small files. I use vim for my journal, quick edits, and data wrangling when I need to get something into a nicer form (most often scraping links to pipe somewhere else). It's a great interface for editing temporary data.
Also, knowing Vim if you ever need to SSH into a remote machine is a must in my eyes. Nano feels sluggish once you get a feel for Vim, and, as the article mentions, you can fine Vim almost everywhere you go.
- hannofcart 6y agoVSCode is very customisable. So you can make it behave exactly like your vim (+plugins) setup behaves.
- RMPR 6y agoNot quite, or maybe I'm the one not doing things the right way, when I tried to make VsCode behave like Spacemacs there was always these annoying things where you'll have the feeling that you're better off using the mouse: for example when you're editing, you can't close the sidebar without focusing it and firing Ctrl+E, I eventually discovered an emulation made by a bunch of people[0], it was great, but for things like Git, I still needed the mouse whereas in Spacemacs you can use the excellent Magit which is entirely keyboard focused. 1: https://github.com/VSpaceCode/VSpaceCode https://github.com/VSpaceCode/VSpaceCode
- patrec 6y agoNot true. VSCode lacks some very fundamental functionality, like proper (non-linear) undo and the vim plugin basically does not support any ex commands (other than s, which works different as well). Having said that, I think the VSCode vim plugin gives a quite good experience overall.
- krebs_liebhaber 6y agoWhy not use one of the many publicly-available add-ons that add Vim bindings to VS Code? Pretty much every IDE has at least one of those - as an Emacs person, I envy it.