Question 1

How do I write a Neovim plugin in Ruby?

Accepted Answer

Start by creating a Ruby script that uses the Neovim gem to attach via RPC, define handlers, and spawn it as a job from Lua. Refer to the example_remote_module.rb and .lua files in the repository for concrete patterns.

Question 2

Neovim Ruby vs Lua for plugins?

Accepted Answer

Neovim Ruby is best for Ruby developers or legacy Vim plugins, offering RPC control and compatibility. Lua is native to Neovim, with lower latency and a larger plugin ecosystem. Choose based on language preference and performance needs.

Question 3

How to migrate a Vim Ruby plugin to Neovim?

Accepted Answer

Use the compatibility layer with :ruby commands supported by the gem. Test your plugin with Neovim's RPC setup and adjust any Vim-specific APIs that might not translate directly, as detailed in the linked documentation.

Question 4

What are remote modules in Neovim Ruby?

Accepted Answer

Remote modules are Ruby scripts that define custom handlers and are spawned as jobs from Lua via jobstart. They replace the old remote plugin system and allow extended functionality through RPC, with examples provided in the spec files.

Question 5

Does Neovim Ruby support TCP connections?

Accepted Answer

Yes, the Neovim gem supports attaching via TCP in addition to Unix sockets, enabling flexible remote control or distributed editor scripting scenarios as outlined in the usage documentation.

Question 6

How to debug Ruby scripts in Neovim?

Accepted Answer

Debug using standard Ruby tools since scripts run externally. Attach to the RPC session, monitor logs, and leverage the Neovim::Client API for interaction. The Rubydoc documentation provides guidance on client methods and error handling.

Neovim

What is Neovim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions