Zac Bergquist

Also stuck here 🤔 I'm not sure how https://github.com/atom/github gets around this.

Seems like it shouldn't be so hard to invoke `gocode close` when the package is deactivated, but I don't think we want to run an asynchronous tool lookup when we're...

Sounds like a great idea - there's been quite a few issues since gometalinter moved away from go get and towards pre-packaged binaries .

Thanks for pointing this out. We do, indeed, just take the first project path. In a multi-project workspace it turns out to be difficult to tell which project a particular...

Its almost certainly autocomplete that is slowing things down for you and not linters. Based on the output above, you are working in a module (`GOMOD` is set, and your...

Not actively working this, but if somebody wants to pick it up feel free. The auto-languageclient package gets you almost all of the way there. The challenge you'll run into...

You want to actually use the auto language client package, as opposed to replacing the gocode call only. This will register to provide more than just autocomplete from gopls (lint...

@james-lawrence we actually did a fair amount of work preparing for the Go language server (which is where you'll get most of the modules support) by leveraging atom-ide-ui for most...

Those are the tools go-plus uses to provide various editing features. They are installed in your `$GOPATH`, which defaults to `~/go`.

No updates at this point. I'd like to wait to get more experience with vgo both personally and see more use in the wild to help inform what to build.