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
For example a common pattern of passing environmnet variables:
$ env DB_HOSTNAME="localhost" bash -c "echo ${DB_HOSTNAME}"
errors with:
env: ‘localhost’: No such file or directory
This is because adjacent symbol and string is considered as two tokens, so it is the same as:
env DB_HOSTNAME= localhost
A workaround is to wrap the whole thing in quotes, but it is not very nice:
env "DB_HOSTNAME=localhost"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
For example a common pattern of passing environmnet variables:
errors with:
This is because adjacent symbol and string is considered as two tokens, so it is the same as:
A workaround is to wrap the whole thing in quotes, but it is not very nice:
The text was updated successfully, but these errors were encountered: