gist.github.com does this!

https://gist.github.com/ChuckHa/8548627

I think the documentation about go workspaces is just a simple approach and it's expected the community will eventually settle on a way to manage this in a non-global fashion.

I'm guessing everyone wants something slightly different and it would be pointless for Go to have One Way hence all the alternatives here.

What makes the recommended approach in the workspace documentation "global"?

I implemented the suggestions in this gist on a new branch here:

https://github.com/ChuckHa/goenv/tree/inve

I'm not sure I like it better though because it unsets $PS1 and other variables that get set in .bash_profile.

Thanks for pointing this out, I hadn't found it.

This is pretty cool, thanks for sharing.

Awesome, I won't pretend to be a bash expert. Any interest in opening a PR?

Naw, just go ahead and commit that if you like. That's too much easier to be worth the fork/checkout/commit/push/pull request cycle work in this case.

Understandable - but it's pretty easy to do small modifications like that using Github's edit feature. Everything but the editing itself is pretty much hidden away.

Did not know that. Thanks!