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

golang stop working after upgrade to 1.11 #11217

Closed
jvillasante opened this issue Aug 26, 2018 · 13 comments
Closed

golang stop working after upgrade to 1.11 #11217

jvillasante opened this issue Aug 26, 2018 · 13 comments
Labels
Go stale marked as a stale issue/pr (usually by a bot)

Comments

@jvillasante
Copy link

I'm very new to go, but after the upgrade to go 1.11 it seems that gocode stopped working.

Company: backend (company-go :with company-yasnippet) error "GOCODE PANIC: Please check your code by "go build"" with args (candidates ur)
Company: An error occurred in auto-begin

It was working fine before the upgrade.
Any thoughts/

@asenyshyn
Copy link
Contributor

nsf/gocode is not maintained anymore use https://github.com/mdempsky/gocode

@robbyoconnor
Copy link
Contributor

If you're using modules -- good luck -- it's not supported yet.

@andres-lowrie
Copy link

^^ Is it on the roadmap to support modules?

@robbyoconnor
Copy link
Contributor

@andres-lowrie -- When tooling is updated, sure -- currently neither go-langserver, which is used in for lsp, nor gocode support it. There is an issue tracking this in the gocode repo.

@ihaveadrame
Copy link

I think it's time to support the module.
Gopls already supports modules but does not correctly recognize modules on spacemac,
There are compatibility issues that need to be resolved, and these problems no longer exist on vscode.

@robbyoconnor
Copy link
Contributor

robbyoconnor commented Aug 13, 2019 via email

@ihaveadrame
Copy link

I solved my problem, gopls is ok!!

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Aug 13, 2020
@mdempsky
Copy link

mdempsky commented Aug 20, 2020

Hi. I'm not a Spacemacs user, but I work on the Go project.

Is Spacemacs enabling company-go / gocode by default? If so, can it be switched to use lsp-mode / gopls by default instead?

gopls is the Go project's officially supported tool for code completion. (Unlike mdempsky/gocode, which was best effort.)

@robbyoconnor
Copy link
Contributor

robbyoconnor commented Aug 20, 2020 via email

@mdempsky
Copy link

I understand users can override the settings. My understanding though is Spacemacs is meant to provide users with good defaults. And if company-go / gocode isn't supported and isn't working, why is it the default instead of lsp-mode / gopls?

@p554157atch
Copy link

The default behavior with spacemacs and go layer is, it keeps autocomplete mode disabled, and enables the company-mode, which then enabled company-go by default.
This is incorrect behavior.

What is even worse is that gocode works sometimes and gives correct suggestions but when you start importing packages, then there is no error or warning things start to fail and company-mode tries to make guesses and gives wrong suggestions.

I spent a lot of time debugging this issue and finally gave up.

@duianto duianto added Go and removed stale marked as a stale issue/pr (usually by a bot) labels Sep 14, 2020
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Oct 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Go stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

8 participants