Kaedys

I feel like this is caused by `.gvm/scripts/function/find_local_pkgset`. This uses the anonymous function syntax style of: ``` function { # ... } ``` The other files use the named function...

@bdeanindy https://github.com/golang/go/issues/20888 ```1.4.2 cannot be used to bootstrap on osx. Brew should have the special version of 1.4.2 that is patched to work on osx, otherwise use 1.8.3 to bootstrap```...

You can fix this on a version-by-version basis using `gvm pkgenv`, and then changing the `export GOPATH; GOPATH=""` line to point at your normal `GOPATH`. However, you have to do...

@adam-hanna you don't need to set `$GOBIN`. If unset, it is automatically inferred as `$GOPATH/bin`, or if `$GOPATH` is not set, `~/go/bin` (since `$GOPATH` is inferred to be `~/go` if...

You have to edit the pkgenv _before_ you set default, because the `--default` flag _copies_ the specified pkgenv to a separate default pkgenv file that you can't directly edit, at...

@pecigonzalo Simply edit the pkgenv for the relevant version (in this case, `system`) again, and then call `gvm use --default` again. Exact same sequence of commands as above. Basically, think...

> How do you use the `pkgenv`... nothing I type shows. I already regret going the `gvm` way. Couldn't things be made a little easier? Literally just type `gvm pkg`....

> https://github.com/golang/go/wiki/SettingGOPATH Not even slightly helpful. Read the thread maybe? The issue is that GVM automatically configures itself with version-specific GOPATHs, despite a single global GOPATH being a common (I...

Duh, that's in the documentation. The problem is that you have to do that again for every new version of Go you install using GVM. The ask is for some...

This is not stale and is still requested.