Introduce binstubs to set RUBYOPT for development #181
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.
Because
syntax_suggest
is a default gem you can get conflicts when working on this project with Ruby 3.2+. To fix conflicts you can disable loadingsyntax_suggest
as a default gem by using then environment variableRUBYOPT
with the value--disable=syntax_suggest
. TheRUBYOPT
environment variable works the same as if we had entered those flags directly in the ruby cli (i.e.ruby --disable=syntax_suggest
is the same asRUBYOPT="--disable=syntax_suggest" ruby
). It's needed because we don't always directly execute Ruby and RUBYOPT will be picked up when other commands load ruby (rspec
,rake
, orbundle
etc.).There are some binstubs that already have this done for you. Instead of running
bundle exec rake
you can runbin/rake
. Binstubs provided:bin/rake
bin/rspec