Joe Fitzgerald

Can you please try `gocode close && gocode drop-cache && go get -u github.com/nsf/gocode`?

Try `which -a gocode` to see if you have multiple copies of `gocode in your path`. If that doesn't work, are you open to a screen sharing session to figure...

`which -a gocode` - do you have multiple gocode binaries in your path?

Are you open to a screen sharing session to figure this out? If so, please join the `#go-plus` channel in one of these Slack teams, and then direct message me...

You're going to need to be more specific than that. Please post a reproduction, contrasting the actual outcome with the expected outcome.

Please file an issue at https://github.com/nsf/gocode.

You're welcome to provide that wrapper. This isn't a priority for me. The built in autocomplete-plus provider is disabled by default by go-plus. Try I checking that option, as it...

You need to restart Atom after unchecking the "Suppress the provider built-in to autocomplete-plus". Then, you may need to scroll down the list to see the fuzzy matches.

@sudhirj yikes! Makes me wonder if it's an issue with go itself? I've seen a few Sierra - specific changes in go 1.7 RC1. Seems like the gocode autocomplete daemon...

@sudhirj are you still experiencing your issue with multiple gocode processes? I'm running on macOS Sierra beta now, and not experiencing the issue. Try `gocode close && go get -u...