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
-
I didn't know before that having multiple Neovim instances is bad
In my case I have this lsp module. I load that module whenever I use the command LoadProject. So my alias looks like this.
-
Loooking for help "translating" some vim script settings into lua
If you wish, you can take a look at my config for goyo
-
Build your first Neovim configuration in lua
neovim config
-
neovim configuration files for LSP.
Here is a simple configuration file I use for a quick setup with no plugins: simple.vim.
-
Created some minimal colorschemes in lua (because why not?)
My config (requires neovim v0.7).
-
Tell me about your workflow!
My dotfiles: all of it. And here is the neovim config.
-
Customising Alpha Dashboard - Query Concerning Configuration
I'm not sure my config is a good example but here it is.
-
Neovim Config
Here are my dotfiles: neovim.
-
What is the most interesting part of your Lua config?
I have a module dedicated to small hacks that allow me to use lua functions where neovim says I can't: bridge
-
Good Neovim Configurations
Mine is just filled with little workarounds and stuff I've added just because. Might not the example of a good config, but there are useful stuff in there.
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?
nvim-lua
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
dotfiles - Eric Lee's Dotfiles for MacOS and Neovim
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
awesome-neovim - Collections of awesome neovim plugins.
developer-workstation-setup-script - Post-install script for Fedora and RHEL 9 clones to create your ultimate development environment
targets.vim - Vim plugin that provides additional text objects
.dotfiles
nvim-compe - Auto completion Lua plugin for nvim
vim-packager - Vim plugin manager that utilizes "jobs" and "pack" features.
lazy.nvim - 💤 A modern plugin manager for Neovim