Add info to add `eval ruby.env` into `.bashrc`
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 32
- Forks
- 5
- Avg merge
- 14h 17m
- Merged PRs (30d)
- 1
Description
In order to execute commands installed by gems, one has to add the line
eval `ruby.env`
to one's .bashrc. This is only stated in this old article but not in the package description or anywhere else. In my opinion this should be more clearly stated as I think this is a useful feature and (not entirely sure) the default behaviour if I were to install it using apt.
Contributor guide
No contributing guide indexed for this repository
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
Compare the package description with the linked 2018 article and the .bashrc setup described in the issue. Update the appropriate package documentation to clearly explain when and why to add eval \ruby.env``; done means users can find this setup without relying on the old article.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100