L3MON4D3

Mhm, that may be an issue with the general setup (I think I can recall encountering something like that), have you looked for similar reports in `lazy.nvim`'s repo?

You could * get the snippet (`ls.session.current_nodes[vim.api.nvim_get_current_buf()].parent.snippet`) * get its trigger (`snip.trigger`) * get its region (`snip:get_buf_position()`) * replace that region with the trigger (see `:h nvim_buf_set_text`) * (reset the...

> If you mean behind as in to the right side of the trigger text, then yes. "Behind" and "in front of" are ambiguous positions. True! Yes, to the right...

Tbh, that is intended as a feature 😅 The intention is that one can always indent snippets with `\t`, and the snippet will insert spaces when expandtab is set, and...

Whew, that is quite the setup😅 Are you sure that toggling expandtab is the best way of going about this? Have you considered checking the conditions when tab is pressed,...

Ah nvm, checking the code of `isn`, we [go to some lengths](https://github.com/L3MON4D3/LuaSnip/blob/15d12dbdad6b5033c78c74bd02d84cddfd710cf6/lua/luasnip/nodes/snippet.lua#L374-L389) to expand tabs :( Mhmm, I guess we can add some options for this though... If we add...

Mhm yeah I guess it makes sense to do this globally, I definitely can't think of a usecase where this would be per-snippet/per-expand xD

I'll definitely still add it, I think there are some cases where it's very hard to work around (for example if a dynamicNode which actually depends on nodes inserts a...

Hi :) It seems a bit like you're conflating what luasnip does and what cmp/cmp_luasnip does, so to make sure that's not the case I'll outline what each of them...

luasnip only expands snippets if the whole trigger matches, cmp_luasnip should also list snippet-items if there is a partial match with the typed text. So `#incl` -> list snippet-items with...