4 ms·
I don't believe it's possible to have a good vimrc without really grasping some elementary concepts like movements, operators, registers, windows etc. I have re
by wodny 10y ago
I don't believe it's possible to have a good vimrc without really grasping some elementary concepts like movements, operators, registers, windows etc. I have recently watched all the Drew Neil's VimCasts[1] and after just a couple of hours I've realized I was missing a lot for at least 10 years. There is also quite a good presentation on YouTube by Max Cantor "How to Do 90% of What Plugins Do (With Just Vim)"[2]. Instead of treating a single vimrc as the best one it's useful to skim through dotfiles and plugins of some influential vim users like Drew Neil[3] and Tim Pope[4]. BTW VimCasts are accompanied by a book. The second edition[5] includes changes introduced by Vim 8.0.
[1]: http://vimcasts.org/episodes/ http://vimcasts.org/episodes/
[2]: https://www.youtube.com/watch?v=XA2WjJbmmoM https://www.youtube.com/watch?v=XA2WjJbmmoM
[3]: https://github.com/nelstrom/dotfiles https://github.com/nelstrom/dotfiles
[4]: https://github.com/tpope https://github.com/tpope
[5]: https://pragprog.com/book/dnvim2/practical-vim-second-edition https://pragprog.com/book/dnvim2/practical-vim-second-editio...
- rcdmd 10y agoI would also recommend Daniel Miessler's tutorial.[1] [1]: https://danielmiessler.com/study/vim/ https://danielmiessler.com/study/vim/
- heycato 10y ago+1 for the Max Cantor presentation - I mostly use stock vim now because of that video... also you can get a lot of mileage from combining :read with shell commands. I like this approach as it forces me to level up my bash.