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
Thanks for all your work writing and maintaining coc-go :)
Maybe that's one for the FAQ or an enhancement request to use the gopls in the user's PATH if it exist:
When using coc-go concurrently with vim-go, it is possible that gopls in daemon mode (-remote=auto) is launched with an incompatible versions. This causes gopls connections to the gopls server be dropped with little debugging information in CocInfo, even with verbose mode. I first fixed this by adding go.goplsUseDaemon: false to the CocConfig but ended up with go.goplsPath: "vim-go's gopls binary" to ensure that I would use the same binary as vim-go.
The text was updated successfully, but these errors were encountered:
elauriault
changed the title
vim-go compatibilty
vim-go w/gopls interroperability
Oct 3, 2020
Thanks for all your work writing and maintaining coc-go :)
Maybe that's one for the FAQ or an enhancement request to use the gopls in the user's PATH if it exist:
When using coc-go concurrently with vim-go, it is possible that gopls in daemon mode (-remote=auto) is launched with an incompatible versions. This causes gopls connections to the gopls server be dropped with little debugging information in CocInfo, even with verbose mode. I first fixed this by adding go.goplsUseDaemon: false to the CocConfig but ended up with go.goplsPath: "vim-go's gopls binary" to ensure that I would use the same binary as vim-go.
The text was updated successfully, but these errors were encountered: