Prevent snippet completion popup after typing space

[huesersohn]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.completion, mini.snippets

Question

I use mini.completion with mini.snippets and whenever I type a space the completion menu with snippets pops up. Is there a way to prevent this and to only have snippets be completed after a non-space character is typed?

[echasnovski]

This doesn't happen with most types of configuration. For example, it doesn't happen for me in Lua filetypes.

The common workflow is that the completion window is automatically shown after typing keyword character or a LSP completion trigger character. My guess is that there is a configuration that adds space (i.e. " ") as a completion trigger character. Could you please execute the following command that will print the capabilities of the active LSP server: :lua vim.fn.append('.', vim.split(vim.inspect(vim.lsp.get_clients({buf = 0})), '\n')). Then look for all instances of server_capabilities.completionProvider.triggerCharacters field (there will probably be several) and see which characters are present there.

[huesersohn]

Interesing, for me in Lua files lua_ls contains this:

triggerCharacters = { "\t", "\n", ".", ":", "(", "'", '"', "[", ",", "#", "*", "@", "|", "=", "-", "{", " ", "+", "?" }

In PHP files it was the TailwindCSS server that has a space (and lua_ls was also present despite ft = "lua"; then I disabled the lazydev plugin and now it is no longer active when editing PHP files).

But also with lazydev disabled I have a space in the triggerCharacters in lua_ls.

Can I edit the tiggerCharacters in the server config?

[echasnovski]

Interesing, for me in Lua files lua_ls contains this:

Oh, my bad. I forgot that I adjust that manually.

Can I edit the tiggerCharacters in the server config?

Of course. If you use Neovim>=0.11 and vim.lsp.enable() approach, then it is the matter of creating an 'after/lsp/lua_ls.lua' file that returns a table with a relevant on_attach method. Here is an example. The similar approach is for other LSP servers by replacing the lua_ls file name with LSP server's name (which is used in vim.lsp.enable()).

[huesersohn]

Thank you!