How to update VS Code GOPATH when running my code in VS Code terminal?
In Ubuntu, I have changed my GOPATH variable via bash terminal. In VS Code it is now showing updated path with Go: current GOPATH
command.
However, when I run go run *.go
I get an error that it can not find my package from my old GOPATH. I tried disabled Go extension, but the error is the same. I even set my new GOPATH in settings.json in VS Code.
go visual-studio-code
add a comment |
In Ubuntu, I have changed my GOPATH variable via bash terminal. In VS Code it is now showing updated path with Go: current GOPATH
command.
However, when I run go run *.go
I get an error that it can not find my package from my old GOPATH. I tried disabled Go extension, but the error is the same. I even set my new GOPATH in settings.json in VS Code.
go visual-studio-code
1
where did you "update your GOPATH"? its probable that the file you updated it in (.eg maybe ~/.bashrc) has not been reloaded by your terminal session, if it is in ~/.bashrc for example that would usually get loaded the next time you launch a terminal, you could force the execution by typing. ~/.bashrc
in terminal, you can also type echo $GOPATH in terminal to verify what value it is using
– SwiftD
Jan 2 at 18:10
I changed it with command in bashexport GOPATH=/media/mygocode
. When I typego env
I can see it is updated.
– Hrvoje T
Jan 2 at 18:13
However, now I reopened my terminal and it showed again old GOPATH. So I updated it only temporarily? How to make this change persistent?
– Hrvoje T
Jan 2 at 18:15
1
yes, if you just run the command in terminal it will be temporary - just the life of that session - I would suggest add it to the bottom of ~/.bashrc, then you can exec the file with. ~/.bashrc
for immediate change - it will then get run every time you launch a terminal
– SwiftD
Jan 2 at 18:18
I putexport GOPATH=/path/to/my/custom/workspace
in my.bashrc
. Restarted for loading in session and started VS Code. Voila, it works now. Thanks!
– Hrvoje T
Jan 2 at 19:00
add a comment |
In Ubuntu, I have changed my GOPATH variable via bash terminal. In VS Code it is now showing updated path with Go: current GOPATH
command.
However, when I run go run *.go
I get an error that it can not find my package from my old GOPATH. I tried disabled Go extension, but the error is the same. I even set my new GOPATH in settings.json in VS Code.
go visual-studio-code
In Ubuntu, I have changed my GOPATH variable via bash terminal. In VS Code it is now showing updated path with Go: current GOPATH
command.
However, when I run go run *.go
I get an error that it can not find my package from my old GOPATH. I tried disabled Go extension, but the error is the same. I even set my new GOPATH in settings.json in VS Code.
go visual-studio-code
go visual-studio-code
asked Jan 2 at 18:05


Hrvoje THrvoje T
4742922
4742922
1
where did you "update your GOPATH"? its probable that the file you updated it in (.eg maybe ~/.bashrc) has not been reloaded by your terminal session, if it is in ~/.bashrc for example that would usually get loaded the next time you launch a terminal, you could force the execution by typing. ~/.bashrc
in terminal, you can also type echo $GOPATH in terminal to verify what value it is using
– SwiftD
Jan 2 at 18:10
I changed it with command in bashexport GOPATH=/media/mygocode
. When I typego env
I can see it is updated.
– Hrvoje T
Jan 2 at 18:13
However, now I reopened my terminal and it showed again old GOPATH. So I updated it only temporarily? How to make this change persistent?
– Hrvoje T
Jan 2 at 18:15
1
yes, if you just run the command in terminal it will be temporary - just the life of that session - I would suggest add it to the bottom of ~/.bashrc, then you can exec the file with. ~/.bashrc
for immediate change - it will then get run every time you launch a terminal
– SwiftD
Jan 2 at 18:18
I putexport GOPATH=/path/to/my/custom/workspace
in my.bashrc
. Restarted for loading in session and started VS Code. Voila, it works now. Thanks!
– Hrvoje T
Jan 2 at 19:00
add a comment |
1
where did you "update your GOPATH"? its probable that the file you updated it in (.eg maybe ~/.bashrc) has not been reloaded by your terminal session, if it is in ~/.bashrc for example that would usually get loaded the next time you launch a terminal, you could force the execution by typing. ~/.bashrc
in terminal, you can also type echo $GOPATH in terminal to verify what value it is using
– SwiftD
Jan 2 at 18:10
I changed it with command in bashexport GOPATH=/media/mygocode
. When I typego env
I can see it is updated.
– Hrvoje T
Jan 2 at 18:13
However, now I reopened my terminal and it showed again old GOPATH. So I updated it only temporarily? How to make this change persistent?
– Hrvoje T
Jan 2 at 18:15
1
yes, if you just run the command in terminal it will be temporary - just the life of that session - I would suggest add it to the bottom of ~/.bashrc, then you can exec the file with. ~/.bashrc
for immediate change - it will then get run every time you launch a terminal
– SwiftD
Jan 2 at 18:18
I putexport GOPATH=/path/to/my/custom/workspace
in my.bashrc
. Restarted for loading in session and started VS Code. Voila, it works now. Thanks!
– Hrvoje T
Jan 2 at 19:00
1
1
where did you "update your GOPATH"? its probable that the file you updated it in (.eg maybe ~/.bashrc) has not been reloaded by your terminal session, if it is in ~/.bashrc for example that would usually get loaded the next time you launch a terminal, you could force the execution by typing
. ~/.bashrc
in terminal, you can also type echo $GOPATH in terminal to verify what value it is using– SwiftD
Jan 2 at 18:10
where did you "update your GOPATH"? its probable that the file you updated it in (.eg maybe ~/.bashrc) has not been reloaded by your terminal session, if it is in ~/.bashrc for example that would usually get loaded the next time you launch a terminal, you could force the execution by typing
. ~/.bashrc
in terminal, you can also type echo $GOPATH in terminal to verify what value it is using– SwiftD
Jan 2 at 18:10
I changed it with command in bash
export GOPATH=/media/mygocode
. When I type go env
I can see it is updated.– Hrvoje T
Jan 2 at 18:13
I changed it with command in bash
export GOPATH=/media/mygocode
. When I type go env
I can see it is updated.– Hrvoje T
Jan 2 at 18:13
However, now I reopened my terminal and it showed again old GOPATH. So I updated it only temporarily? How to make this change persistent?
– Hrvoje T
Jan 2 at 18:15
However, now I reopened my terminal and it showed again old GOPATH. So I updated it only temporarily? How to make this change persistent?
– Hrvoje T
Jan 2 at 18:15
1
1
yes, if you just run the command in terminal it will be temporary - just the life of that session - I would suggest add it to the bottom of ~/.bashrc, then you can exec the file with
. ~/.bashrc
for immediate change - it will then get run every time you launch a terminal– SwiftD
Jan 2 at 18:18
yes, if you just run the command in terminal it will be temporary - just the life of that session - I would suggest add it to the bottom of ~/.bashrc, then you can exec the file with
. ~/.bashrc
for immediate change - it will then get run every time you launch a terminal– SwiftD
Jan 2 at 18:18
I put
export GOPATH=/path/to/my/custom/workspace
in my .bashrc
. Restarted for loading in session and started VS Code. Voila, it works now. Thanks!– Hrvoje T
Jan 2 at 19:00
I put
export GOPATH=/path/to/my/custom/workspace
in my .bashrc
. Restarted for loading in session and started VS Code. Voila, it works now. Thanks!– Hrvoje T
Jan 2 at 19:00
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011088%2fhow-to-update-vs-code-gopath-when-running-my-code-in-vs-code-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011088%2fhow-to-update-vs-code-gopath-when-running-my-code-in-vs-code-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
where did you "update your GOPATH"? its probable that the file you updated it in (.eg maybe ~/.bashrc) has not been reloaded by your terminal session, if it is in ~/.bashrc for example that would usually get loaded the next time you launch a terminal, you could force the execution by typing
. ~/.bashrc
in terminal, you can also type echo $GOPATH in terminal to verify what value it is using– SwiftD
Jan 2 at 18:10
I changed it with command in bash
export GOPATH=/media/mygocode
. When I typego env
I can see it is updated.– Hrvoje T
Jan 2 at 18:13
However, now I reopened my terminal and it showed again old GOPATH. So I updated it only temporarily? How to make this change persistent?
– Hrvoje T
Jan 2 at 18:15
1
yes, if you just run the command in terminal it will be temporary - just the life of that session - I would suggest add it to the bottom of ~/.bashrc, then you can exec the file with
. ~/.bashrc
for immediate change - it will then get run every time you launch a terminal– SwiftD
Jan 2 at 18:18
I put
export GOPATH=/path/to/my/custom/workspace
in my.bashrc
. Restarted for loading in session and started VS Code. Voila, it works now. Thanks!– Hrvoje T
Jan 2 at 19:00