Tracking: Outdated {neo}vimPlugins #359498
Comments
khaneliman
added
the
5. scope: tracking
Unlike Neovim, Vim has a pretty stable API, so it's not uncommon for Vimscript plugins that haven't been maintained in 10 years to still be useful. |
Yeah, that makes sense. I do see a lot of vim in here. I'll try and separate the list better. |
khaneliman
changed the title
|
I hope, that when I will rewrite pluginupdate.py, I could check whether a repository is archived and throw a warning. |
I wonder if you would need an API key for that. See #90257 for previous attempts. IIRC, the choice was made to not require the usage of an github token. Now I would like to have the licence and even better the plugin description. One hackish way to do that would be to add another overlay "metadata.nix". This way you can regenerate only generated.nix or if you have a token both generated.nix and metadata.nix. In terms of eval it's still a perf hit. Back to this MR, if only we had cache hits statistics that would make the job a lot easier ! I myself have a minimalistic approach regarding nix vim plugins: I install only fondamental or complex plugins via nix and install small simple ones via https://github.com/nvim-neorocks/rocks.nvim. I find installing vim plugins via nix a bit too complex for most plugins which are simple and developed dynamically. To sum up, I will follow the decision of the other maintainers :) |
The script uses XML API right now, if we switch instead to REST API, we won't need any additional requests to get description and other information for meta. It can be optimized even further -- to do 1 request per plugin by using GraphQL API, but that requires token.
You can't get more exhaustive than we are now. Maybe with some automatic system for discovering and adding plugins, like https://github.com/m15a/flake-awesome-neovim-plugins. |
|
We also have nvim-neorocks/robert (see |
Oh that's interesting. Would be nice to query against. |
|
awesome info @PerchunPak ty. I did know about https://github.com/m15a/flake-awesome-neovim-plugins . @mrcjkb the readme is stingy with details: |
Created a quick script just to see what we have for plugins that might be abandoned or haven't been updated in a long time.
We could double check these and see if they don't have a new version because they are abandoned, forked, just stable maintenance, etc. We can then decide to remove any that might be safe to just stop maintaining.
Checklist
Neovim Plugins
Unknown Plugins
Vim Plugins
Notify maintainers
@NixOS/neovim
Note for maintainers: Please tag this issue in your PR.
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: