Join Us In Slack: https://gophers.slack.com | #go-plus | https://gophersinvite.herokuapp.com to get access
run every time you launch a new terminal
Hello. Iam having a problem with missing errors when saving. But when I build the go application manually in the terminal it returns a bunch of errors. Back in the days go-plus also showed all build errors this when saving the application in Atom. How should I fix this? There is one console error in Atom: "[Package-Deps] Unable to get package info for json-lint-provider" Maybe this is related?
I am running Atom version 1.8 by the way. Thanks for any help.
You have a few options: 1) set it as a user environment variable and log out / log in 2) system environment variable and reboot or 3) set the config in go-config package settings for GOPATH
@ErthyLoL_twitter
'C:\Users\roese>go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\BTSync\Developing\Go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1'
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\BTSync\Developing\Go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1'
I think my GOPATH is set, the only question is if correctly.
(Sorry for not quite understanding everything and for such a prompt response @joefitzgerald !)
That looks good, right?
I tried to add C:\BTSync\Developing\Go\bin to my PATH. Is restarting Atom enough to test it out, or do I need to relog/restart?
You have to do this every time you update your go version
might have found it by inspecting some stuff in gocode... seems I had an old brew install lingering around...
I mean this bit ->
gocode close && go get -u github.com/nsf/gocode
Now everything works fiiiiiiiiiine.
it tells me about compilation errors and
go vet, so it's not that broken
welp, i think i was missing the
environment plugin for atom. installed that, re-installed gocode, and it works
chat is great for rubber ducking sometimes
running
gocode close && go get -u github.com/nsf/gocode will always do the trick
had a chat with Nathan Bass on Slack resulting in: joefitzgerald/autocomplete-go#44
in essence: you need to close the gocode daemon after you upgrade go to a new version
Hi @joefitzgerald , thank you, the trick work for me perfect!!!.
@joefitzgerald Wow, I am having the same issue with autocomplete not working anymore. I think it was after upgrading Go. I also used brew this time to install Go. I tried the recommended: gocode close && go get -u github.com/nsf/gocode However this didn't seem to do anything for me.