Skip to content

Adjacent symbols and strings considered as two tokens #156

@dundalek

Description

@dundalek

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"

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions