cmd/go: can only run "go env" in certain places #35409
I've historically checked out my Go development trees to $HOME/go. (where it naturally falls if you do
That habit predates the new automatic GOPATH value of $HOME/go.
But that led to this surprising behavior on a new machine I was benchmarking:
In $HOME/go ...
And can run
But if I cd down into
Is this working as intended?
Can it be made more helpful if I'm holding it wrong?