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.
dotfiles
-
Courses on NeoVim Configuration/Lua (for neovim)
If you need some guidance, feel free to steal from my overworked config
-
Any point in switching to packer?
Check this out https://github.com/rebelot/dotfiles/blob/master/nvim/lua/plugins.lua
- kanagawa.nvim with laststatus=3
-
Is it possible to show which LSP is responsible for the current completion menu item?
It is possible, but the feature is not guaranteed to be stable. Check format function in https://github.com/rebelot/dotfiles/blob/master/nvim/lua/plugins/cmp.lua
paq-nvim
- [Neovim] Gestionnaire de packages basé à Lua
-
Is Packer still maintained?
If you want a dead simple package mamage that only puts packages in opt and start, you can use paq.nvim
-
Introducing LazyVim!
Is there anyone here who can share some feedback on how much lazy.nvim has been better than what you were using previously? If my context helps, I'm using paq-nvim, previously was using packer.
- Neovim - Workflow para Java, C# e JS/TypeScript (Atualização com Neovim 0.8 e LSP)
-
Cannot update plugins
This was a problem when I was using paq as my manager, now I have the same problem with packer. It never happened when I wanted to install new plugins, only on updating. With packer I have a workaround: after it fails to sync it allows to re-run all failed jobs, and each times about a half of failed jobs fail again, others update successfully, so I can iteratively sync everything, but that's a terrible waste of time;
-
Help with plug
Options: - packloadall command family and maybe git submodules - minpac which is a thin utility around the above - vim-plug - old but still popular for it does the job - packer.nvim is a popular choice for lua configs, never got to using it myself - paq-nvim is another often mentioned lua solution - dozens of other solutions
-
which plugin manager are you using?
that sounds like paq, but slow?
-
New to Rust. How to setup Nvim as IDE?
On my Neovim setup, I simply have the following plugins. I use paq as a plugin manager:
-
Neovim: Plugins to get started
paq.nvim
What are some alternatives?
neovim-config - A Neovim setup using Lua
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
nvim-defaults.vim - Neovim default settings for Vim
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
kanagawa.nvim - NeoVim dark colorscheme inspired by the colors of the famous painting by Katsushika Hokusai.
awesome-neovim - Collections of awesome neovim plugins.
dotfiles_skeleton - robust and beginner friendly dotfile skeleton
targets.vim - Vim plugin that provides additional text objects
dotfiles
nvim-compe - Auto completion Lua plugin for nvim
Launch.nvim - 🚀 Launch.nvim is modular starter for Neovim.
lazy.nvim - 💤 A modern plugin manager for Neovim