tag: Lua

Plugins in vim and neovim are usually just collections of .vim (and in neovim’s case .lua) files which can be loaded or interacted with from your own config once you downloaded them. They are usually managed with git and cloned to your machine when you install them. There is a history of plugin managers in vim and neovim going back almost a decade, but nowadays the neovim community seems to have settled on lazy.nvim. Now, before you go and install it, I want to present you with other options, as well as my opinion on each one, and how plugins are “actually” implemented by these plugin managers. ...

In this section I will cover more details about configuring and extending neovim as an editor. This will partially apply to vim as well, so I will explicitly mention anything that is neovim-exclusive. It’s also kind of over the place with random topics, as I don’t really see an order here, just pick and choose what you’re interested in :) As I already mentioned, neovim heavily invests into Lua. This means that you can write your entire configuration using Lua! (There are some exceptions to this, such as the autoload/ directory, but for the most part everything just works with Lua) ...