Add a test to verify server's environment is passed to spawned process
chipsenkbeil opened this issue · comments
It's unclear if this happens. I'd like to test something like printing the $HOME
directory because today that environment variable either gets evaluated locally with distant spawn
or just gets printed verbatim as $HOME
.
I want to make sure that spawn actually supports feeding in the current environment variables. If it does, this is an issue with the client capturing and sending over the environment variables.
As discussed in rust-lang/rust#95400, none of the variable substitution happens because this is not run in a shell. With the addition of --cmd
for spawn, you can now do: distant spawn -c 'sh -c "echo $PATH"'
to do variable substitution.
Won't actually write a test. Manual check good for me.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.