Trying to get used to VIM, moving away from VScode. Any tips?
@UwUbuntUwU
If you're gonna use plugins then try to keep them organized, it will help. I use neovim and ended up using lua to handle configs. There's some handy videos online if you search for vim/neovim personal configs and setup guides.
Follow
@UwUbuntUwU
+1 for NeoVim. Good choice if you are coming from VSCode, it just has saner defaults.
My Vim is loaded with plug-ins, but I probably never use half of them (realistically none of them), sometimes I end up running it with an empty config over ssh just to avoid starting all this. Yes, this class browser looks nice, but I just want to comment that line out. Should've probably used sed for that anyway 🤣
@word_of_the_nerd
@UwUbuntUwU
While we're at it, an immensely useful plugin for commenting lines out: https://github.com/tpope/vim-commentary
Just select what you want commented out using "v", then "gcc" — done! Easy to remember shortcut.
You can, of course, do the same to un-comment lines. And it takes the file type into consideration and handles comments in css and shell scripts differently.
@word_of_the_nerd