You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I already commented out imenu-integration of go-mode, that's not the problem.
If I uninstall go-mode and open the file, eglot correctly starts gopls
If I literally open a go file and start eglot afterwards, gopls correctly loads.
The problem is rather hard to debug. In my particular project, out of 20? times gopls and eglot start to interact properly
If I open a very small project (so that gopls has probably not much to analyse) go-mode, eglot and gopls always work.
Maybe it is a problem with windows pre-maturely reporting back successful process spawning, maybe it is gopls pre-maturely returning control to the os while rpc thread is still blocked? It seems a rather interacted timing issue of which go-mode may actually not be the culprit but rather a promoter.
Reporting here nonetheless as without go-mode eglot and gopls work.
The text was updated successfully, but these errors were encountered:
Using emacs 29 on windows from https://github.com/kiennq/emacs-build/releases/tag/v29.169.20221201.4a23421
When using go-mode eglot failes to properly connect with gopls
The actual error message I get is
I already commented out imenu-integration of go-mode, that's not the problem.
The problem is rather hard to debug. In my particular project, out of 20? times gopls and eglot start to interact properly
If I open a very small project (so that gopls has probably not much to analyse) go-mode, eglot and gopls always work.
Maybe it is a problem with windows pre-maturely reporting back successful process spawning, maybe it is gopls pre-maturely returning control to the os while rpc thread is still blocked? It seems a rather interacted timing issue of which go-mode may actually not be the culprit but rather a promoter.
Reporting here nonetheless as without go-mode eglot and gopls work.
The text was updated successfully, but these errors were encountered: