I still use vim :) with my own set of plugins managed by vim-plug.
ctrlp and nerdtree are my top two essential plugins.
I think the best way to get started with vim is the hard way, to copy settings and plugins one at a time from example vimrcs and understand each line that is going on. It takes more work, but I actually love being in full control of my editor.
I must admit, though 🙈 every once in a while I open up VSCode, usually it is only if I'm working in a large unfamiliar project. When there are lots of directories and files and I don't know the project structure, VSCode makes it a little easier for me to search and grep around.
L.A. based web developer slowly parsing through Stack Overflow. If you like hot web dev tips or stories about being a freelancer, check out my newsletter: https://codenutt.substack.com/p/coming-soon
That's probably true, but I like to introduce people to Vim inside of VS Code with the VIM extension. It's a great way to let people get their feet wet without committing a lot of time.
L.A. based web developer slowly parsing through Stack Overflow. If you like hot web dev tips or stories about being a freelancer, check out my newsletter: https://codenutt.substack.com/p/coming-soon
I like that idea. It didn't work for me, though. I would fall back to what I knew and avoid using Vim motions. To me, it's like learning any language...immersion is key.
I'm also a Vim user and totally agree that you have to learn it the hard way. I've tried to take shortcuts, but I've found that all the time I've invested reading the help and actually learning the ins and outs of how Vim works has been well worth it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I still use vim :) with my own set of plugins managed by vim-plug.
ctrlp and nerdtree are my top two essential plugins.
I think the best way to get started with vim is the hard way, to copy settings and plugins one at a time from example vimrcs and understand each line that is going on. It takes more work, but I actually love being in full control of my editor.
I must admit, though 🙈 every once in a while I open up VSCode, usually it is only if I'm working in a large unfamiliar project. When there are lots of directories and files and I don't know the project structure, VSCode makes it a little easier for me to search and grep around.
agreed.
it's not harder than emacs
That's probably true, but I like to introduce people to Vim inside of VS Code with the VIM extension. It's a great way to let people get their feet wet without committing a lot of time.
I like that idea. It didn't work for me, though. I would fall back to what I knew and avoid using Vim motions. To me, it's like learning any language...immersion is key.
That's true Jared, I will also give it a try, the hard way.
I'm also a Vim user and totally agree that you have to learn it the hard way. I've tried to take shortcuts, but I've found that all the time I've invested reading the help and actually learning the ins and outs of how Vim works has been well worth it.