Investigate how to support version managers that do not setup gem executables
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2k
- Forks
- 281
- Avg merge
- 2h 14m
- Merged PRs (30d)
- 6
Description
During RubyConf, I paired with someone using direnv + nix to manage Ruby and Bundler to install gems. The direnv + nix combo doesn't allow gem executables to be invoked, despite installing gems successfully. Even in this person's terminal, invoking gem executables was not possible.
The problem is even more complex because Bundler was configured to install gems in vendor/bundle and the developer had no idea where gems installed via gem install end up.
I'm wondering if we can instead force the installation path for the Ruby LSP to be inside the VS Code storage paths and then we launch the executable from there. It might make launch more robust for these scenarios.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Ruby LSP gem installation and executable launching for the direnv + nix setup, including Bundler's vendor/bundle path and the proposed VS Code storage paths. Reproduce the environment and determine whether the Ruby LSP can launch its executable from a controlled installation path; done means this setup works reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100