3 ms·
I've jumped ship from vim to vscode ~5 years ago, for better or worse, after having been a vim person for previous ~20. There are still things I miss which are
by baq 3y ago
I've jumped ship from vim to vscode ~5 years ago, for better or worse, after having been a vim person for previous ~20.
There are still things I miss which are impossible to replicate in vscode without breaking it, but I feel the out of the box experience and reduction in configuration complexity is a rather large net positive.
vim is still what I use to edit stuff via ssh and in docker images, though.
- fragmede 3y agoI wouldn't say I've jumped ship, simply because I'm still using both. I've got vim in a terminal and a vscode window up, and it's not seamless, but I wield the two together to get the job done. Debugging is done in vscode, but vscode doesn't have all the vim stuff in, so in still attached there, plus it runs in a terminal and vscode doesn't.
- lll-o-lll 3y agoDo you use one of the vim plugins in vscode?
- baq 3y agoI tried and they kinda sorta 95% work, but then you hit the missing motions or a keybinding conflict or some extension issue and it’s either fight the thing or go the opinionated way.