simplify remote plugins

[justinmk]

Problem

The design, and usage, of remote plugins can be simplified, as described in https://github.com/neovim/neovim/issues/27949

tl;dr:

• remove the concept of "remote plugins"
• instead, any Ruby module that imports the neovim-ruby client can call register_handler to handle requests from Nvim
• "remote plugins" become plain old Lua plugins which call RPC methods on the Go module

Solution

• [x] Apply the above proposal to neovim-ruby client.
  • [x] "Encapsulate the stdio related code in a helper function." Neovim.start_remote()
  • [x] Update docs https://github.com/neovim/neovim-ruby/pull/107
• [x] Deprecate the old rplugin interface.
• [ ] Update handling of g:ruby_host_prog, so it can point to ruby
  • Transitional phase: neovim-ruby-host will continue to be accepted; the path to ruby will be derived by inspecting the shebang in neovim-ruby-host.
• [ ] (Nvim 0.12) Remove old rplugin-related code

Related

• https://github.com/neovim/pynvim/issues/567
• https://github.com/neovim/go-client/issues/167

[alexgenco]

Update handling of g:ruby_host_prog, so it can point to ruby

(Nvim 0.12) Remove old rplugin-related code

Is there anything to do for these in this repo? These seem like changes to neovim itself, except maybe deleting the remote plugin code once nvim 0.12 lands.

[justinmk]

Correct. Just for tracking/visibility