-
Notifications
You must be signed in to change notification settings - Fork 128
GVM support? #74
Comments
This seems like a reasonable feature. Is there anything go-plus is doing that is specifically causing issues, or should we be detecting GVM use somehow and then invoking it to determine go / GOPATH paths? |
👍 |
Using Atom 1.1 when I have instance already running with another project launching gvm use go1.5
# Now using version go1.5
export GOPATH="$(pwd):$GOPATH"
atom . Seems like environment variables are not passed. When working with single project commands above are enough to get gvm working with go-plus. Also I usually do first run without adding GOPATH to install tools globally. Would be handy to have list of commands for manual install as an alternative to automatic install. |
When Atom is already running, any subsequent attempts to launch atom result in a new window being launched from the original process. So you're right, the environment for Windows 2...n will be ignored in favor of the environment for Window 1. There may be a workaround to this, but I'm not aware of it if there is. |
Looking at goexecutable.coffee, it seems like go-plus doesn't inspect |
GVM adds go binaries to
|
I don't think that's relevant. GVM also updates GOROOT, and it is the "standard" way to locate the Go binaries, so supporting it would make all tools (including GVM) work. |
GOROOT is required to be set when you put a runtime built for a standard location in a non-standard location. If you set the appropriate environment variables when building from source to your desired target location, GOROOT does not need to be set. Regardless, go-plus doesn't care. You should ensure you launch atom from the terminal - in which your environment is set as you need - and things should just work. I agree I could add inspection of GOROOT to the detection logic, but in general the PATH should be used to specify the path to your desired runtime (and precedence among multiple installed runtimes). You should remove the various paths from your configuration, check the option for environment overrides configuration, and make sure you launch atom from terminal or iterm2 instead of Dock/Finder/Spotlight/open. |
+1 on this. I am able to set my GOPATH manually in the settings, but I keep getting the following warning: |
I had trouble at first and then relaunched from terminal with no problem. Using gvm w/go1.5.3. Thanks @joefitzgerald! |
@iDev0urer workspaces are experimental feature in Go 1.5 in 1.6 they will be enabled. |
Closing this due to age. |
It would be nice to have https://github.com/moovweb/gvm support. GVM set the gopath to something like
/home/antonio/.gvm/pkgsets/go1.3.3/global
so you could derive the current go installation and toolsThe text was updated successfully, but these errors were encountered: