nvim-conf
packspec
nvim-conf | packspec | |
---|---|---|
5 | 7 | |
125 | 204 | |
- | 1.5% | |
9.4 | 4.8 | |
5 days ago | 2 months ago | |
Lua | Lua | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nvim-conf
- Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
-
Comparing different approaches to packer
My plugin definitions
-
File Structure for Adjusting Plugin Options
I keep plugin configurations in my lua/user/plugin/ directory. If the plugin's options are short, I keep them in a file called misc.lua, otherwise I create a separate file with the name of the plugin. Check out my config to see what I mean.
-
What do you want to know about the process of converting an init.vim to init.lua setup?
Here is my configuration currently, nearly all Lua. Here is what it looked like when it was still VimScript (quite messy).
-
GitHub - b0o/mapx.nvim: A better way to create key mappings in Neovim
Please head over to the README for more examples, or check out my config to see how I actually use Mapx.
packspec
- This Week In Neovim #31 – Mon Feb 13 2023
-
Introducing Luarocks-Tag-Release - Publish your Neovim plugins to LuaRocks
It looks like there's a WIP package specification that might also support source = luarocks://.
-
Standardizing Neovim package management API - could or should this be a thing? Let’s talk about it!
I was hoping you would clarify exactly what you're proposing so I could forward the appropriate link, otherwise I'm just guess based off a vague (but long) post. Based on other replies in this reddit post, I'm not the only one confused by your ambiguous and likely incorrect terminology. It sounds like you're looking for a specification, which exists https://github.com/nvim-lua/nvim-package-specification, it just isn't well adopted. There's also countless Github issues and discussions about this on IRC which you could find by a simple Google search. It really just depends on what you're alluding to which is why I linked what an API was so you could be more specific. If you're looking for the plugin managers API (notice the qualifier) to be consistent, then that's not a good idea since the API of the plugin manager is what differentiates them, it's like saying all programming languages should be the same, the only thing different should be the backend (e.g. gcc vs llvm). The consistency should be at a different layer (thus the plugin spec).
-
Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
packspec, a package specification for neovim to address the dependency issue
-
Opinion on better plugin management?
There is an issue for it: https://github.com/nvim-lua/nvim-package-specification/issues/23
What are some alternatives?
CodeArt - Use NeoVim as general purpose IDE
lazy.nvim - 💤 A modern plugin manager for Neovim
nvim-config - A modern Neovim configuration with full battery for Python, Lua, C++, Markdown, LaTeX, and more...
luarocks - LuaRocks is the package manager for the Lua programming language.
astro.nvim - Faster Neovim Configuration
vscode-eslint - VSCode extension to integrate eslint into VSCode
lazy-require.nvim - Require as little as possible. Do as little work as possible. Spend hours shaving off milliseconds
lsp-format.nvim - A wrapper around Neovims native LSP formatting.
mapx.nvim - 🗺 A better way to create key mappings in Neovim
neovim - Vim-fork focused on extensibility and usability
vim-resize-mode - A Vim mode for easier window resizing
fabn