3 ms·
Why? No, seriously, why do you think you have to switch if you are productive with VSCode? I used to be all in with Vim and then Emacs many years ago. I can m
by jmmv 4y ago
Why?
No, seriously, why do you think you have to switch if you are productive with VSCode?
I used to be all in with Vim and then Emacs many years ago. I can manage pretty well with both to this day. But I moved onto VSCode a few years ago and… it’s very nice. It just works out of the box. I have tried to move back to Emacs for example, but the lack of trivial and good remoting features and the lack of great LSP integration are hard to overcome.
Nowadays I still use vim for quick or repetitive edits (learn how to record and replay macros; they are a game changer), but otherwise spend all of my time in VSCode with its Vim mode enabled.
And to be fair, I only use the Vim mode in VSCode because I moved from macOS to Windows and I could not stand the Windows native shortcuts.
- wara23arish 4y agoI remember I found setting up remote connections for VSCode harder than emacs. isnt emacs just M-x ssh … and ure done?