-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which plugins use :UpdateRemotePlugins ? #29270
Comments
I used https://github.com/gelguy/wilder.nvim. It's a better interface for the cmdline mode. Better fuzzy finding, auto-completion, and UI. And it's really good imo! :D I am somewhat addicted to having some extra colors for popups so it helps me navigate things better. |
https://github.com/Shougo/deoplete.nvim They are legacy plugins. Because I have already migrated to denops based plugins. https://github.com/roxma/nvim-yarp nvim-yarp does not use |
cursorless.nvim currently registers node functions manually on its own, which means neither another plugin can do it in their own plugin nor can it be done in the default rplugins.vim (with “:UpdateRemotePlugins”) or it will conflict with cursorless.nvim. If that happens, the first plugin registering node functions will win and the other will fail. Deprecating ":UpdateRemotePlugins" will be a game changer :) Production plugin: https://github.com/hands-free-vim/cursorless.nvim |
https://github.com/wookayin/semshi (a original repo: https://github.com/numirias/semshi) A semantic highlighting (using extmarks) plugin for python. People may want to use LSP semantic highlight instead, but a few python users have been using it. Potentially, the plugin also may benefit from a straightforward refactoring, so it can completely eliminate the use of |
User feedback request
Your feedback is requested to help us understand what "remote plugins" you are using.
Which plugins do you use that require
:UpdateRemotePlugins
?Please comment below with a URL to the plugin(s). Or upvote 👍 comments that already mention plugins that you are using.
This will help us migrate existing "remote plugins" to the new model proposed in #27949
The text was updated successfully, but these errors were encountered: