| ▲ | skydhash 4 hours ago | |
There are the Practical Vim[0] and Modern Vim[1] by D. Neil And the VimL Primer[2] by B. Klein But Vim is a whole culture that starts with ed(1), the standard editor. You do edit based on line numbers and regex addressing and commands. Then there was ex(1) that added more features. vi(1) added a `visual` mode to ex(1), and some commands can now be done in relation to the position of the cursor. Vim is the improved version of vi(1), a lot more commands and a scripting language. The plugin system is similar to everything that was unix at that time, relying on a variable like $PATH. Any path added to that variable (runtimepath for vim), should follow some patterns for subdirectories and the file will be loaded according to a certain logic. Plugin managers actually manage that variable and do a few things aside (isolating plugins, downloading from forges,...) [0]: https://pragprog.com/titles/dnvim2/practical-vim-second-edit... [1]: https://pragprog.com/titles/modvim/modern-vim/ [2]: https://www.oreilly.com/library/view/the-viml-primer/9781680... | ||
| ▲ | sodapopcan 4 hours ago | parent [-] | |
There is also Learn VimScript the Hard Way, which is of course a bit outdated, but it does help to know "legacy" vimscript. vim9script is very intuitive and easy to learn for anyone who knows any OO language from the past 30 years. The difficulty comes in learning the ins and outs of Vim itself (when it comes to scripting it, that is). | ||