You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just has support for setting environment variables:
export RUST_BACKTRACE := "1"
test:
cargo test
But does not support unsetting environment variables
unset RUST_BACKTRACE
test:
cargo test
In the ideal scenario, the environment variable has an equivalent value to being unset (0 in the case for RUST_BACKTRACE)
Unfortunately, some programs, crates, and/or libraries treat an unset environment variable different than even an empty string, so it would be helpful to be able to unset these at the global level instead of remembering to sprinkle in the manual method everywhere:
test:
#!/bin/bash -x
unset RUST_BACKTRACE
cargo test
The text was updated successfully, but these errors were encountered:
nickbabcock
changed the title
Allow unset environment variables
Allow unsetting environment variables
Jul 8, 2022
This definitely seems useful, and the unset FOO seems reasonable. The best way to implement this is probably with a new Item variant, Item::Unset(String), which causes exported variables to be unset.
Just has support for setting environment variables:
But does not support unsetting environment variables
In the ideal scenario, the environment variable has an equivalent value to being unset (0 in the case for
RUST_BACKTRACE
)Unfortunately, some programs, crates, and/or libraries treat an unset environment variable different than even an empty string, so it would be helpful to be able to unset these at the global level instead of remembering to sprinkle in the manual method everywhere:
The text was updated successfully, but these errors were encountered: