Can VSCode editing be as fast as Emacs/Vim?
4 comments
Yeah, it's so much easier to create / edit beyond shortcuts. That being said, it does take more effort to get things like intellisense working
You should start with vim, but graduate to something much closer to an IDE
https://github.com/verdverm/neoverm
You should start with vim, but graduate to something much closer to an IDE
https://github.com/verdverm/neoverm
Do you have examples? Of things that are faster in vim?
Generally all movement and bulk edits.
One thing I learned recently is !! and how to use it to inject any program output at the current line. You can also use the current selection as input to that command. Write some code in vim, run !!bash or !! python and the output is replaced the code. Really helpful for doc writing and showing output
One thing I learned recently is !! and how to use it to inject any program output at the current line. You can also use the current selection as input to that command. Write some code in vim, run !!bash or !! python and the output is replaced the code. Really helpful for doc writing and showing output
Just install the VIM bindings on VS Code. They are good enough (Don't flame me) and most of the speed you get from VIM is in the modal editing language. VS Code will give you other speed ups that are often difficult to set up in VIM so you get the best of both worlds.
I don’t have a problem with anything on vsc - in fact, I use it when I ssh into servers because I like the nice “at a glance” file UI, and I don’t have to cd & ls to see where and what everything is.
Unlearning all the vsc keystrokes, shortcuts, and tools is going to be a serious time commitment, but I’m a young guy and have a long career ahead of me. If vim is really that much faster, I’d be willing to take the performance hit for long term growth.