-
I wanted to make a post here but I get shadow banned for not having enough reddit karma :< (I used these to make catppuccin.nvim startup in 1ms)
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.
-
It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.
-
nvim-lint
An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.
It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.
-
I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.
-
:lua vim.pretty_print(vim.mpack.decode(vim.mpack.encode({some = { thing = false }}))) used by impatient.nvim
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
vim-illuminate
illuminate.vim - (Neo)Vim plugin for automatically highlighting other uses of the word under the cursor using either LSP, Tree-sitter, or regex matching.
+1, I avoided .setup in vim-illuminate and had a github comment explaining why it started and the alternative I went with, https://github.com/RRethy/vim-illuminate/issues/112. Got a lot of push-back on reddit for that. Happy to see some others dislike that useless convention.
-
+1. I've already taken the first step.
-
I'm pretty sure we got started down the .setup road because of this article by norcalli a few years ago. It was published when plugins started using Lua and suddenly I went from seeing one or two plugins using .setup to literally every single plugin use it.