Document VS Code Ruby LSP setup - #23995
Merged
MikeMcQuaid merged 1 commit intoSep 16, 2026
Merged
Conversation
HaraldNordgren
force-pushed
the
document-ruby-lsp-vscode-setup
branch
from
September 16, 2026 07:06
a165f7f to
70eebf5
Compare
MikeMcQuaid
reviewed
Sep 16, 2026
MikeMcQuaid
left a comment
Member
There was a problem hiding this comment.
I don't think this quite makes sense being in CONTRIBUTING. Maybe in FAQ or Tips and Tricks section in docs?
HaraldNordgren
force-pushed
the
document-ruby-lsp-vscode-setup
branch
from
September 16, 2026 08:01
70eebf5 to
779fd2a
Compare
Contributor
Author
|
Good point, moved to the existing VS Code section in |
HaraldNordgren
force-pushed
the
document-ruby-lsp-vscode-setup
branch
2 times, most recently
from
September 16, 2026 08:04
e280891 to
b369f4a
Compare
rubyVersionManager, customRubyCommand and bundleGemfile in .vscode/settings.json are "machine"-scoped, so VS Code never applies them from a workspace's settings.json. Nothing in the repo told contributors this, so anyone with the Ruby LSP extension just hit a bare "zsh: parse error near '&&'" with no path to a fix.
HaraldNordgren
force-pushed
the
document-ruby-lsp-vscode-setup
branch
from
September 16, 2026 08:11
b369f4a to
32eba94
Compare
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
2 participants
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.
rubyVersionManager,customRubyCommandandbundleGemfilein.vscode/settings.jsonare "machine"-scoped, so VS Code never actually applies them from a workspace's settings.json (Shopify/ruby-lsp#4120 would fix this upstream). Nothing in the repo told contributors this, so anyone with the Ruby LSP extension just hit a barezsh: parse error near '&&'with no path to a fix. This documents the workaround.brew benchmarkresults.brewcommands to reproduce the bug?brew lgtm(style, typechecking and tests) locally?Disclosure: drafted with Claude Code assistance. I reviewed the change and reasoning and will answer questions myself.