Replies: 2 comments 3 replies
-
|
Thanks for the information. Did you configure the LSP launch command according to our docs? Since the LSP hooks into the project's bundle to inspect dependencies, the command you use to launch should include Anything we need to update in the docs? |
Beta Was this translation helpful? Give feedback.
-
|
I don't remember doing that, specifically. I was, and I guess still am, assuming that installing the lsp via the Mason panel was enough. Given I'm using Mason and your docs call out that using Mason may cause errors I'm not surprised I'm having this issue. :) and I'm far from a lua/neovim expert. Maybe I need to configure it like your LazyVim section. The BTW, these were the errors I was getting in the log. Maybe it's the shebang in the Maybe after installing ruby-lsp in my 3.3.7 install and reinstalling via Mason it reset the shebang line. It appears I should be installing and configuring the lsp directly instead of in Mason but I figure that requires running it in one ruby all the time until I decide to install it in a newer ruby? |
Beta Was this translation helpful? Give feedback.
-
|
Mason and rbenv are definitely at odds here. Normally I'd expect Mason to install the binstub with the generic |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: I updated my require('mason-lspconfig').setup({
ensure_installed = {},
handlers = {
ruby_lsp = function()
require('lspconfig').ruby_lsp.setup({
cmd = { vim.fn.expand("~/.rbenv/shims/ruby-lsp") },
})
end,
}
})I then switched to a project in ruby 3.2.6 where ruby-lsp had not been installed and the rbenv shim appears to have done the trick. Here's what the log reported when it initialized ruby-lsp in this other project. My suggestion for the docs might be updating your section on Mason with something like what I did with a specific |
Beta Was this translation helpful? Give feedback.
-
|
That important block section at the top applies to every editor. I think it would be a bit odd to link to it from Mason only, since it applies to everything in those docs. And repeating the same callout for every editor seems a bit much. Not sure if we could somehow make the important block stand out more, to ensure it's not skipped. |
Beta Was this translation helpful? Give feedback.
-
I'm running Neovim with Mason and I was frequently seeing ruby-lsp exit with status 1. I'm also running rbenv where my global is 3.3.7 and my site .ruby-version is also 3.3.7. However, I kept seeing in the lsp.log file that ruby-lsp was running
bundle installin 3.3.6!I discovered that I hadn't yet installed ruby-lsp in 3.3.7. I did that but that didn't even fix it. What eventually did fix it was that after installing it in 3.3.7 I had to go back to Mason and update ruby-lsp. Now ruby-lsp thinks it's running in 3.3.7.
It's been a while since I read any documentation for ruby-lsp. If it's listed somewhere that if your default ruby is updated you need to also update ruby-lsp I didn't remember it.
Hopefully this helps someone in the future.
(e)
Beta Was this translation helpful? Give feedback.
All reactions