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
Hi - I have a question about using this plugin along with Navigator. I'd like to be able to use Navigator for the GUI bits and for common keybindings and I'd like to still be able to use the nice functionality from this plugin for things like inlay hints and such. Enabling the default lsp config on this plugin doesn't do anything unless I also disable gopls in Navigator, and then I lose the functionality from Navigator. I can import the gopls config from this plugin with local goplscfg = require 'go.lsp'.config() and use that as the lsp config in Navigator and that kind of works, but it seems like there is some kind of start up race and I'm only getting the right functionality some of the time. What is the right way to set up these two plugins so that I can use Navigator as the source of truth for the lsp configuration and still use this plugin?
The text was updated successfully, but these errors were encountered:
Hi - I have a question about using this plugin along with Navigator. I'd like to be able to use Navigator for the GUI bits and for common keybindings and I'd like to still be able to use the nice functionality from this plugin for things like inlay hints and such. Enabling the default lsp config on this plugin doesn't do anything unless I also disable
gopls
in Navigator, and then I lose the functionality from Navigator. I can import the gopls config from this plugin withlocal goplscfg = require 'go.lsp'.config()
and use that as the lsp config in Navigator and that kind of works, but it seems like there is some kind of start up race and I'm only getting the right functionality some of the time. What is the right way to set up these two plugins so that I can use Navigator as the source of truth for the lsp configuration and still use this plugin?The text was updated successfully, but these errors were encountered: