-
Notifications
You must be signed in to change notification settings - Fork 174
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
Not sure what this warning it, but it is consistent #1508
Comments
Typically, if you have bundle installed already and the extension keeps showing you that it needs to bundle install it means that it is selecting the wrong version of Ruby. Do you use any version managers (e.g.: I should also mention that the Ruby LSP doesn't support |
I use RBEnv now, switched off RVM as it caused way too many problems with VSCode. I do use Standard, so I guess that for now, I cannot use the Ruby LSP. |
Adding While we don't yet support Standard as a formatter, you can still use the Ruby LSP with formatting disabled if you want. Just configure your enabled features to pick the ones you want. "rubyLsp.enabledFeatures": {
"formatting": false
// keep everything else enabled
} |
Thank you! Will try all this out and see how it goes. |
I actually did have the correct setting, yet that prompt to install the bundle continues.. this is why I quit VSCode before, it just cannot handle the fact I have projects open that each have their own version of Ruby running... hence with it's global configuration it has all sorts of per project issues. |
Do you have multiple projects open in the same instance of VS Code? If that's the case, indeed the Ruby LSP doesn't support that well yet. |
Absolutely! I see no reason not to work that way. But I do understand, VSCode is probably under-whelming for this use case. I keep hearing how RubyMine is actually the only editor that truly works at a pro-level... but I have never tried it with any gusto. Maybe I should! |
There aren't any VS Code limitations as far as I know. The Ruby LSP just doesn't support multiple workspaces yet. I've opened #1510 to track the work to support it. |
…er-protocol-3.17.0.2 Bump language_server-protocol from 3.17.0.1 to 3.17.0.2
I use Standard. In my bundles I added ruby-lsp. I have this VSCode ruby-lsp added to my VSCode.
I still get that little nag dialog about not having ruby-lsp in the bundle, and asking to bundle install it.
What is up with that? I get it, complex stuff. But it makes using this language server, suspect? Not sure it matters. But I am curious as to what causes this, and perhaps what the workaround is to get that to not happen.
The text was updated successfully, but these errors were encountered: