Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Code Completion fails for getgb.io / slide based projects #153

Closed
conikeec opened this issue Dec 10, 2015 · 3 comments
Closed

Code Completion fails for getgb.io / slide based projects #153

conikeec opened this issue Dec 10, 2015 · 3 comments

Comments

@conikeec
Copy link

Hey

I have been attempting to migrate majority of my projects to getgb.io based vendoring/build system.
For any such projects, I use direnv to add the vendor folder (for the specific project) to $GOPATH environment variable.

Where is $GOOT and $GOPATH being set.

My current alias to initiate Visual studio from the command line is

!/bin/bash

export GOPATH=$(PWD)/vendor:$GOPATH
VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $*

Yet my $GOPATH is not being reset in visual studio to include the vendor directory

Am I missing anything here?

@sevein
Copy link

sevein commented Mar 7, 2016

I've been experiencing this same issue with OSX and the fish shell. I've found that it only works when your launcher script exports a new environment variable that has not been defined before but it will fail with variables like GOPATH that were probably defined already. It could be related to @lukehoban's comment: #220 (comment).

Alternatively, I'm looking at defining go.gopath in my workspace settings, it works now but I think it'd be best when variables like workspaceRoot are expanded in settings so I don't have to use absolute paths. Related issues: microsoft/vscode#3759 and microsoft/vscode#2809.

@ramya-rao-a
Copy link
Contributor

@conikeec @sevein
There have been quite a few changes in both VS Code and the Go extension since last March.
Do you still have issues with GOPATH?

@ramya-rao-a
Copy link
Contributor

Closing this issue as it is very old and we havent heard back from the OP.

@conikeec @sevein if you do have any updates, please comment here and I can re-open the issue

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants