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
Last year, some tools installed by :GoInstallBinaries were not compatible with GO111MODULE=on. This was tracked as issue #2248.
Commit 1237fa0 (later tweaked with commit 4899a0e) fixed it by enforcing GO111MODULE=off during the installation.
While this was necessary, that has the drawback of polluting the user's GOPATH.
A year later, I did a manual test just now and found that this is not necessary anymore!
export GO111MODULE=on
go get github.com/klauspost/asmfmt/cmd/asmfmt
go get github.com/go-delve/delve/cmd/dlv
go get github.com/kisielk/errcheck
go get github.com/davidrjenni/reftools/cmd/fillstruct
go get github.com/rogpeppe/godef
go get golang.org/x/tools/cmd/goimports
go get golang.org/x/lint/golint
go get golang.org/x/tools/gopls
go get github.com/golangci/golangci-lint/cmd/golangci-lint
go get github.com/fatih/gomodifytags
go get golang.org/x/tools/cmd/gorename
go get github.com/jstemmer/gotags
go get golang.org/x/tools/cmd/guru
go get github.com/josharian/impl
go get honnef.co/go/tools/cmd/keyify
go get github.com/fatih/motion
go get github.com/koron/iferr
This succeeded.
As such, I'd request to remove this hack. In practice, it's removing references to Restore_modules in plugin/go.vim so it should be a simple change. Filing a formal bug to confirm such change would be accepted.
The text was updated successfully, but these errors were encountered:
It's also worth pointing out that GO111MODULE must still be set in order to set it appropriately regardless of what the user has it configured as to make sure the right thing is done. The relevant section in the go's help is worth considering to give you more context: https://golang.org/cmd/go/#hdr-Module_support
Although some of the binaries are not modules, Go can still handle that situation without polluting GOPATH. Vim-go has taken advantage of that for since last year. Although vim-go changes into a temporary directory, it's not used, though there is one possible future case where using GO111MODULE=off may be useful again, so I'm going to leave the code in for now even though it's not used at the moment.
Last year, some tools installed by
:GoInstallBinaries
were not compatible withGO111MODULE=on
. This was tracked as issue #2248.Commit 1237fa0 (later tweaked with commit 4899a0e) fixed it by enforcing
GO111MODULE=off
during the installation.While this was necessary, that has the drawback of polluting the user's GOPATH.
A year later, I did a manual test just now and found that this is not necessary anymore!
This succeeded.
As such, I'd request to remove this hack. In practice, it's removing references to
Restore_modules
in plugin/go.vim so it should be a simple change. Filing a formal bug to confirm such change would be accepted.The text was updated successfully, but these errors were encountered: