Daniel Hååvi

I opened an issue yesterday that is quite similar, but reversed, trying to containerize go, not atom: #832 The problem is the same, go-plus does not find go, albeit go...

I now also tried to link `/usr/local/go` or `/usr/local/go/bin` to my faked environment. No success. I'd like to understand how go-plus finds/validates the go binary and tools.

Interesting, it then really _should_ work. I just tried (on MacOS host): ``` $ GOOS=linux PATH=/Users/[REDACTED]/fakego/bin:$PATH atom . $ # no success, try another way and check commands: $ export...

I put together a small repo to help you reproduce the issues: https://github.com/dhaavi/go-in-docker At least I got goimports to work (Go code is formatted after save), so the basics seem...

Thank you for your input. > 1. Our logic for finding the `go` tool was a little silly. We found the tool, then executed `go env` to find its `$GOROOT`,...

I monkey-patched your fix for finding the go tool and made some progress. - `goimports` seems to work fine, it formats the code on save (that was my bad) -...

I played around with a couple different packages now. `gocode` does work in other circumstances. Will further update this issue with more details when I get an understanding of the...

Fixed another issue in https://github.com/dhaavi/go-in-docker

Pull request https://github.com/joefitzgerald/go-plus/pull/835 in combination with "Additional test args" set to `-coverprofile=/tmp/dockenv/go/coverage.out` fixes coverage. Atom now correctly shows test coverage.

I am further updating https://github.com/dhaavi/go-in-docker as I find and fix issues. It already works pretty well. There is still an issue with gocode: It still does not do suggests for...