Snippet session gets started on opening bracket

[0x1B56B]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.snippets

Question

Hi there. I have a question about snippet sessions. In my case a snippet session is started, as soon as I type an opening bracket. For example (Golang source):

fmt.Printf(•)∎

I type all letters to the first bracket ( (which triggers a auto close) and the session is started inside the brackets. The snippet plugin is configured as follows:

add({ source = 'echasnovski/mini.snippets' }) local gen_loader = require('mini.snippets').gen_loader require('mini.snippets').setup({ snippets = { gen_loader.from_lang() } }) MiniSnippets.start_lsp_server()

Inside my $HOME/.conf/nvim/snippets/ dir is a file named go.json with the content of the go.json file from friendly snippets: https://raw.githubusercontent.com/rafamadriz/friendly-snippets/refs/heads/main/snippets/go.json.

I'm not sure if its a bug or if I'm using the plugin the wrong way. Can please someone help? Thanks :) ... And thanks for the great mini plugins, I really appreciate them!

[echasnovski]

This looks like you are using completion engine and this is a result of an accepting snippet completion candidate from LSP. This can happen if completion engine has "autoselect" feature - then pressing ( might "confirm" the selection which starts snippet session. Do you use completion engine and (if yes) which one?

I indeed see this with fmt.Printf() + gopls and 'mini.completion'. Here is the behavior:

mini-snippets-in-lsp.mp4

The first time there is no snippet session because completion candidate is not explicitly chosen (as is with default 'mini.completion' setup) and autopair comes from 'mini.pairs' module. The second time it is explicitly chosen, so pressing ( leads to confirmation and snippet insert (i.e. start snippet session).

So all in all, this does seem to be an expected behavior because LSP provides the completion candidate as a snippet of the form fmt.Printf($1)$0. Here are some ways to work around that:

• Disable LSP snippets in gopls. Not entirely sure/remember how to do that.
• Configure completion engine to not "autoselect" the entry in favor of explicitly doing it. For 'mini.completion' it should happen by default (as it sets 'noselect' flag in 'completeopt' option).

Does this answer the question? If not, try to disable LSP and try to reproduce.

And thanks for the great mini plugins, I really appreciate them!

❤️

[0x1B56B]

Hi, thanks for enlightening me :) ... I didn't know that the completion candidate in this case is also a snippet. That makes sense now. I use also gopls and mini.completion. Since this is expected behavior I will not take any action. I was just curious. Thanks :)