Repository navigation
Conversation
Author
|
I have signed the CLA! |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Ruby LSP's code lenses call client-side commands like
rubyLsp.runTestandrubyLsp.debugTest. The VS Code extension implements them, but Neovim doesn't, so choosing Run or Debug fails with "Language server does not support command". ruby-lsp.nvim implements those commands, and Neovim users can't currently find it from the editors page.I've been building ruby-lsp.nvim and using it daily with coworkers for most of this year, and it feels stable enough to share more widely.
Implementation
Adds a ruby-lsp.nvim subsection under Neovim. It describes what the plugin sets up and its optional neotest, nvim-dap and toggleterm integrations. It shows an install with Neovim's built-in
vim.pack, pinned to released versions, and points to the plugin's README for advanced configuration.It also adds a line in "Additional setup" pointing to the plugin's
:RubyLspShowDependenciescommand as an alternative to theShowRubyDepssnippet.Automated Tests
Documentation only.
Manual Tests
cd jekyll && bundle install && bundle exec jekyll serve