-
Hey! I am encountering an inconvenience with the mechanics of snippet completion. I usually use snippets for writing LaTeX code which involves using multiple snippets at the same time. For example first expand a fraction I use This behavior defeats the point of using snippets for me. If I am not mistaking this behavior is actually caused by neovim? It is specified in https://cmp.saghen.dev/configuration/snippets.html#snippets that "Blink uses the I would expect the completion engine to instead nest all the completions and keep track of all the future positions that should be respected. Maybe its possible to implement a solution inside the blink.cmp? I use LazyVim in my setup if it is necessary to know. Thanks for such a wonderful plugin btw :D |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You'll want to look into using LuaSnip or mini.snippets since the built-in |
Beta Was this translation helpful? Give feedback.
You'll want to look into using LuaSnip or mini.snippets since the built-in
vim.snippet
doesn't support nested snippet sessions: https://cmp.saghen.dev/configuration/snippets#luasnip