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
Removing setting the environment variable fixes some of the script tests, but others fail with a missing path separator in paths. Currently, I'm having trouble finding where $/ is getting used to create the paths.
@oridb, I'm trying to better understand the nature of the problem. cmd/go uses os/exec under the hood, so if these environment variables are not valid on Plan 9, does that imply that some behavior in exec.Cmd also needs to change, or at least have its documentation clarified?
For example, should (*exec.Cmd).Start fail explicitly on Plan 9 if the Env slice contains an entry beginning with /? (Or should it ignore such entries entirely?)
Also simplify platform-dependent handling of the PATH variable,
to make it more like the existing platform-dependent handling for
HOME and TMPDIR.
Reviewed-by: Ian Lance Taylor <firstname.lastname@example.org>
Run-TryBot: Bryan Mills <email@example.com>
TryBot-Result: Gopher Robot <firstname.lastname@example.org>