Skip to content
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

Open
justinmk opened this issue Jun 10, 2024 · 5 comments
Open

Which plugins use :UpdateRemotePlugins ? #29270

justinmk opened this issue Jun 10, 2024 · 5 comments
Labels
api libnvim, Nvim RPC API enhancement feature request plugin plugins and Vim "pack" project-management Neovim project matters (release process, logo, etc.) remote-plugin plugins as RPC coprocesses (node.js, python, etc)

Comments

@justinmk
Copy link
Member

justinmk commented Jun 10, 2024

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

@justinmk justinmk added enhancement feature request api libnvim, Nvim RPC API plugin plugins and Vim "pack" project-management Neovim project matters (release process, logo, etc.) remote-plugin plugins as RPC coprocesses (node.js, python, etc) labels Jun 10, 2024
@justinmk justinmk changed the title Which plugins are using :UpdateRemotePlugins ? Which plugins use :UpdateRemotePlugins ? Jun 10, 2024
@lucario387
Copy link
Contributor

lucario387 commented Jun 10, 2024

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.

@benlubas
Copy link

@Shougo
Copy link
Contributor

Shougo commented Jun 11, 2024

https://github.com/Shougo/deoplete.nvim
https://github.com/Shougo/denite.nvim
https://github.com/Shougo/defx.nvim

They are legacy plugins. Because I have already migrated to denops based plugins.
I support them currently, but if the plugin changes are too big, I will quit the support of them.

https://github.com/roxma/nvim-yarp

nvim-yarp does not use :UpdateRemotePlugins directly, but if neovim-python interface is changed, the plugin must be fixed.

@saidelike
Copy link

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
Sources for the plugin: cursorless-dev/cursorless#2256

@wookayin
Copy link
Member

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 :UpdateRemotePlugins and rplugin decorators.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api libnvim, Nvim RPC API enhancement feature request plugin plugins and Vim "pack" project-management Neovim project matters (release process, logo, etc.) remote-plugin plugins as RPC coprocesses (node.js, python, etc)
Projects
None yet
Development

No branches or pull requests

6 participants