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.
I've been going a little crazy trying to get the go command working in vscode. I may have installed Golang on the system after i tried installing the Go package however the terminal in vscode doesn't recognize the go command while the main Terminal app does.
I have uninstalled and reinstalled the Go package from VS Code 4-5x times including closing and creating new terminal sessions inside the program. Why is the main Terminal app able to access go while the terminal inside vs code isn't?
Can you start VS Code from the main terminal where the go command works using the command code and then see if you can use the go command in the integrated terminal?
Running the go command in the integrated terminal has nothing to do with the Go extension.
It is more likely that the integrated terminal doesn't have the same PATH as your external terminal and is not able to find go
After looking around and echo'ing my $PATH I noticed that go was installed in /usr/local/go/bin while my exported PATH referring to /usr/local/binand some other matches. I just added the exact path to my .bash_profile and everything is working now. Thanks for the feedback.
I've been going a little crazy trying to get the
go
command working in vscode. I may have installed Golang on the system after i tried installing the Go package however the terminal in vscode doesn't recognize thego
command while the main Terminal app does.I have uninstalled and reinstalled the Go package from VS Code 4-5x times including closing and creating new terminal sessions inside the program. Why is the main Terminal app able to access
go
while the terminal inside vs code isn't?OS: OSX
VS Code: v 1.12.2
GoLang: 1.8.3
Go env:
The text was updated successfully, but these errors were encountered: