We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plenv requires bash and its document supports not only bash also zsh, so those have less readability, I think.
According to the POD, it depends on bash, However actually, it may be caused by that "$(plenv init -)" outputs codes in bash for eval.
eval
So the new to do for us is just fix documents like bellow:
bash -c 'eval "$(plenv init -)"'
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Plenv requires bash and its document supports not only bash also zsh, so those have less readability, I think.
According to the POD, it depends on bash, However actually, it may be caused by that "$(plenv init -)" outputs codes in bash for
eval.So the new to do for us is just fix documents like bellow:
bash -c 'eval "$(plenv init -)"'The text was updated successfully, but these errors were encountered: