You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
in GoSublime specifying a $GS_GOPATH or use_gs_gopath cause it to lookup as follows:
the current working directory, e.g. ~/go/src/pkg then $GS_GOPATH will be ~/go/
or the path the current .go file (or last activated .go file if the current file is not .go) e.g. if your file path is /tmp/go/src/hello/main.go then it will be /tmp/go
in vscode-go:
setting go.inferGopath: true should use the current workspace to resolve a suitable gopath,
e.g. $HOME/go/src/github.com/myuser/demoapp then go.gopath will be $HOME/go/
I personally prefer working with multiple windows, which is what is provided right now anyways.
Having this would de-clutter explorer sidebar showing just files relevant to the project. Also prevent accidentally modifying files not related to your project.
The text was updated successfully, but these errors were encountered:
codmajik
added a commit
to codmajik/vscode-go
that referenced
this issue
Feb 2, 2017
in GoSublime specifying a $GS_GOPATH or use_gs_gopath cause it to lookup as follows:
in vscode-go:
go.inferGopath: true
should use the current workspace to resolve a suitable gopath,e.g. $HOME/go/src/github.com/myuser/demoapp then go.gopath will be $HOME/go/
More info:
GoSublime Usage and Tips
I personally prefer working with multiple windows, which is what is provided right now anyways.
Having this would de-clutter explorer sidebar showing just files relevant to the project. Also prevent accidentally modifying files not related to your project.
The text was updated successfully, but these errors were encountered: