Output correct environment path. #3483
Open
Conversation
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
Author
|
The build is failing here:
i noticed that the way the command is being tested is not as the one explained in the documentation of rvm. https://rvm.io/deployment/cron#loading-rvm-environment-files-in-shell-script to fix this i need to know what is the correct way to execute the command, thanks. |
scripts/functions/env
Outdated
Member
There was a problem hiding this comment.
-n is a tad more concise than ! -z for the string-isn't-null test.
| rvm_token=${rvm_token#--} | ||
| rvm_token=${rvm_token//-/_} | ||
| export "rvm_${rvm_token}_flag"=1 | ||
| rvm_ruby_args+=($next_token); |
Member
There was a problem hiding this comment.
this does not look good, the options here do not take arguments and next_token is what's listed after them, could be anything
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Pull requets to fix the "'env' command doesn't operate as expected #3465" issue