Open li1234yun opened 2 years ago
I think we need to make those commands not answer until the go version & go env queries are complete and values to be used by the extension are determined.
I think we need to make those commands not answer until the go version & go env queries are complete and values to be used by the extension are determined.
I agree!
Please think about the vscode may use the command in the config file, such as tasks.json
.
same issue
Change https://go.dev/cl/398155 mentions this issue: src/goMain: require configureLanguageServer for full activation
What version of Go, VS Code & VS Code Go extension are you using?
go version
to get version of Go from the VS Code integrated terminal.gopls -v version
to get version of Gopls from the VS Code integrated terminal.code -v
orcode-insiders -v
to get version of VS Code or VS Code Insiders.Go: Locate Configured Go Tools
command.Share the Go related settings you have added/edited
Describe the bug
When I run vscode command
Go: Current GOPATH
after the vscode started at the first time, I got theundefined is the current GOPATH.
. but I continue to run the same command, I got/Users/lzy/go is the current GOPATH.
.I think the GOPATH may be got correctly by these places:
go env
/echo $GOPATH
/vscode.go.gopath
Steps to reproduce the behavior:
Go: Current GOPATH
undefined is the current GOPATH.
Go: Current GOPATH
/Users/lzy/go is the current GOPATH.
Screenshots or recordings
None