After accepting and with auto_brackets turned on there is no signature info with gopls

[WhoIsSethDaniel]

NVIM v0.12.0-dev-372+g570e62d0f9
Build type: RelWithDebInfo
LuaJIT 2.1.1744317938

blink.cmp: latest main
gopls lsp config: https://github.com/WhoIsSethDaniel/dotfiles/blob/148179009e621c82492fb0e34ca83260fb8ed425/.config/nvim/after/lsp/gopls.lua
blink config: https://github.com/WhoIsSethDaniel/dotfiles/blob/148179009e621c82492fb0e34ca83260fb8ed425/.config/nvim/lua/plugins/blink-cmp.lua

When I have signature.trigger.show_on_accept set to true and completion.accept.auto_brackets.enabled set to true I do not get signature help immediately following the accept when editing go files and using gopls. I do get signature help if I exit insert and re-enter insert after accepting. When editing Lua I do get signature help immediately after accepting, which is what I would expect.

I can get it to work with gopls iff I turn on completeFunctionCalls[1] in the gopls configuration. However when I turn that on I get ghost text within the auto-inserted brackets and to the right of the brackets. It never seems to go away and is very annoying. See below for a copy and paste (the cursor is between the parens):

fmt.Printf(•)∎

Does anyone else see this?
Is there a way to either 1) receive the signature help following accept without setting completeFunctionCalls in gopls or 2) get rid of the ghost text when completeFunctionCalls is turned on?

[WhoIsSethDaniel]

When gopls has completeFunctionCalls turned on it returns this as the newText:

textEdit = {
  newText = "Printf(${1:})",
}

I imagine the ${1:} is at lease part of why the ghost text is showing up. I don't know if that ${1:} is intentional.

blink sees the brackets and skips performing auto brackets, which is as expected.

[WhoIsSethDaniel]

It seems that vim-matchup causes the lsp signature not to be displayed after accept iff auto_brackets is turned on, signature.trigger.show_on_accept is turned on, and gopls's completeFunctionCalls is turned off. I can only replicate the problem when that plugin is enabled. If it is disabled I do not see the problem.

[WhoIsSethDaniel]

Perhaps not surprisingly it has to do with the parentheses matching that vim-matchup performs. Turning off matchparen will make the problem go away. Although doing this also removes much of the primary functionality of vim-matchup.

[WhoIsSethDaniel]

Is there a way to disable/enable vim-matchup directly after accept and after the brackets have been added? Or something similar?

[WhoIsSethDaniel]

If I block go from using kind resolution and force semantic resolution it works as expected: I get auto brackets and I get the function signature. However you must enable semanticTokens in gopls (it's not on by default) and you must turn off completeFunctionCalls in gopls (it's on by default).

[WhoIsSethDaniel]

So iff:

• you are using gopls with blink.cmp
• you are using vim-matchup and have paren matching turned on
• you want auto brackets
• you want the function signature to appear after accepting a completion

you need to:

• block the go filetype for kind resolution by adding go to completion.accept.auto_brackets.kind_resolution.blocked_filetypes (this should force semantic resolution for auto brackets)
• in gopls turn on semanticTokens
• in gopls turn off completeFunctionCalls

[WhoIsSethDaniel]

See followup comments re: mini.snippets. This entire answer may be unnecessary.

[WhoIsSethDaniel]

There are two unanswered, but somewhat tangential, questions asked above:

1. is blink.cmp handling the return correctly from gopls when gopls has completeFunctionCalls turned on? See After accepting and with auto_brackets turned on there is no signature info with gopls #1766 (comment) for details.
2. compatibility with other plugins can be a tricky issue. Should there be some other way to work with vim-matchup? Maybe there is and I just don't know about it.

[WhoIsSethDaniel]

I think the actual problem may be with mini.snippets. Or the interaction between blink.cmp and mini.snippets. If I don't use mini.snippets with blink.cmp and just use whatever blink does by default I have none of the problems mentioned above even when gopls has completeFunctionCalls turned on.