Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"missing Git command" when GOPATH not set #49

mitchlloyd opened this issue Sep 12, 2018 · 2 comments

"missing Git command" when GOPATH not set #49

mitchlloyd opened this issue Sep 12, 2018 · 2 comments


Copy link

@mitchlloyd mitchlloyd commented Sep 12, 2018

Using the default GOPATH (not explicitly setting it) results in an error saying that git is not in PATH (it is):

> retool do
retool: syncing
retool: downloading
retool: fatal err: execution error on "go get -d": go: missing Git command. See
package exec: "git": executable file not found in $PATH
: failed to 'go get' tool: exit status 1

It would be nice if retool worked with the default GOPATH or at least warned if GOPATH isn't set.

> retool version
retool v1.0%
Copy link

@spenczar spenczar commented Mar 11, 2019

retool really isn't prepared for the brave new world of Go modules and GOPATH-less workflows. I'm not sure we can remedy this issue, since it goes quite deep into how the tool works.

It might be time to instead start thinking about how a new retool2 (re2l?) might work, centered around modules. Or, even better, how we might use Go modules to replace any need for retool at all.

Copy link

@natefinch natefinch commented May 13, 2019

Here's a blog post I wrote up explaining how you can avoid needing retool (for many of the basic cases) in the modules world -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants