Wondering why the, afaik, most popular vim/nvim plugin manager, vim-plug, is not listed in plugin managers.
https://github.com/junegunn/vim-plug has more than three times as many github stars as lazy.nvim, which is the plugin manager with most stars in the list here.
Originally created by @oj-lappi on GitHub (Jan 5, 2024).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1031
Wondering why the, afaik, most popular vim/nvim plugin manager, vim-plug, is not listed in plugin managers.
https://github.com/junegunn/vim-plug has more than three times as many github stars as lazy.nvim, which is the plugin manager with most stars in the list here.
<!-- gh-comment-id:1878921875 -->
@fsouza commented on GitHub (Jan 5, 2024):
First item in the check list: https://github.com/rockerBOO/awesome-neovim/blob/HEAD/.github/pull_request_template.md
Could you please expand that explanation? do you mean that vim-plug is not on the list because it also supports vim?
vim-plug is a big part of the eco-system, most of the plugins listed in this repo give examples for installing using vim-plug. I would hope for there to be a well-founded reason for leaving it out.
<!-- gh-comment-id:1879365478 -->
@oj-lappi commented on GitHub (Jan 5, 2024):
Could you please expand that explanation? do you mean that vim-plug is not on the list because it also supports vim?
vim-plug is a big part of the eco-system, most of the plugins listed in this repo give examples for installing using vim-plug. I would hope for there to be a well-founded reason for leaving it out.
The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax
This is clearly not true for vim-plug.
<!-- gh-comment-id:1879375091 -->
@thetic commented on GitHub (Jan 5, 2024):
> The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax
This is clearly not true for vim-plug.
But it's the plugin manager many people would use to install these neovim plugins. It is weird and arbitrary to leave it out. Somehow the fact that vim-plug supports both vim and neovim is a reason not to list it?
And this criterion that it be designed only for neovim is not mentioned in the readme at all, instead it says this is a list of plugins "mostly targeting neovim features". If vim-plug can't be added to the list, can it at least be mentioned more prominently that parts of the ecosystem that also support vim are not listed.
I use neovim every day and just recently came across this repo looking for what the current ecosystem looks like. I was extremely confused when it was not listed. My first thought was that vim-plug was somehow outdated or considered bad practice, and I had to double check what the status of it was.
It is just strange to me that a repo for neovim plugins does not list the most prominent tool used by the community to manage plugins. Lazy.nvim might be challenging that position, but vim-plug clearly has a huge footprint. Searching vim-plug + nvim gives 36.1k "Code" hits in githubs search, compare to lazy.nvims 35.2k
I'm not making a value statement about which is better, but I'm saying it is extremely strange that a tool this popular in the community is not listed.
<!-- gh-comment-id:1879653911 -->
@oj-lappi commented on GitHub (Jan 6, 2024):
But it's the plugin manager many people would use to install these neovim plugins. It is weird and arbitrary to leave it out. Somehow the fact that vim-plug supports both vim and neovim is a reason not to list it?
And this criterion that it be designed only for neovim is not mentioned in the readme at all, instead it says this is a list of plugins "mostly targeting neovim features". If vim-plug can't be added to the list, can it at least be mentioned more prominently that parts of the ecosystem that also support vim are not listed.
I use neovim every day and just recently came across this repo looking for what the current ecosystem looks like. I was extremely confused when it was not listed. My first thought was that vim-plug was somehow outdated or considered bad practice, and I had to double check what the status of it was.
It is just strange to me that a repo for neovim plugins does not list the most prominent tool used by the community to manage plugins. Lazy.nvim might be challenging that position, but vim-plug clearly has a huge footprint. Searching vim-plug + nvim gives 36.1k "Code" hits in githubs search, compare to lazy.nvims 35.2k
I'm not making a value statement about which is better, but I'm saying it is extremely strange that a tool this popular in the community is not listed.
Ok, it seems the readme's description of the repo is stale then, although the discussion in that issue never seemed to reach a conclusion. It just fizzled out.
<!-- gh-comment-id:1882837311 -->
@oj-lappi commented on GitHub (Jan 9, 2024):
Ok, it seems the readme's description of the repo is stale then, although the discussion in that issue never seemed to reach a conclusion. It just fizzled out.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @oj-lappi on GitHub (Jan 5, 2024).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1031
Wondering why the, afaik, most popular vim/nvim plugin manager, vim-plug, is not listed in plugin managers.
https://github.com/junegunn/vim-plug has more than three times as many github stars as lazy.nvim, which is the plugin manager with most stars in the list here.
@fsouza commented on GitHub (Jan 5, 2024):
First item in the check list: https://github.com/rockerBOO/awesome-neovim/blob/HEAD/.github/pull_request_template.md
@oj-lappi commented on GitHub (Jan 5, 2024):
Could you please expand that explanation? do you mean that vim-plug is not on the list because it also supports vim?
vim-plug is a big part of the eco-system, most of the plugins listed in this repo give examples for installing using vim-plug. I would hope for there to be a well-founded reason for leaving it out.
@thetic commented on GitHub (Jan 5, 2024):
This is clearly not true for vim-plug.
@oj-lappi commented on GitHub (Jan 6, 2024):
But it's the plugin manager many people would use to install these neovim plugins. It is weird and arbitrary to leave it out. Somehow the fact that vim-plug supports both vim and neovim is a reason not to list it?
And this criterion that it be designed only for neovim is not mentioned in the readme at all, instead it says this is a list of plugins "mostly targeting neovim features". If vim-plug can't be added to the list, can it at least be mentioned more prominently that parts of the ecosystem that also support vim are not listed.
I use neovim every day and just recently came across this repo looking for what the current ecosystem looks like. I was extremely confused when it was not listed. My first thought was that vim-plug was somehow outdated or considered bad practice, and I had to double check what the status of it was.
It is just strange to me that a repo for neovim plugins does not list the most prominent tool used by the community to manage plugins. Lazy.nvim might be challenging that position, but vim-plug clearly has a huge footprint. Searching vim-plug + nvim gives 36.1k "Code" hits in githubs search, compare to lazy.nvims 35.2k
I'm not making a value statement about which is better, but I'm saying it is extremely strange that a tool this popular in the community is not listed.
@tan-wei commented on GitHub (Jan 8, 2024):
@oj-lappi The repo is "awesome plugins sepcial for Neovim".
@tversteeg commented on GitHub (Jan 8, 2024):
See #574.
@oj-lappi commented on GitHub (Jan 9, 2024):
Ok, it seems the readme's description of the repo is stale then, although the discussion in that issue never seemed to reach a conclusion. It just fizzled out.