L3MON4D3

You could try disabling formatting (or other features, until it works) in `lspconfig.intelephense.setup{}`.

I found the dotfiles of someone who also opened an issue about formatting with intelephense, maybe try their options [link](https://github.com/knowler/dotfiles/blob/a08380648b97508845eddbc590e32b411500278a/.config/nvim/lua/lsp-config.lua#L86-L108)

The problem disappearing with vsnip is because they manually track changes done to text whereas luasnip uses extmarks. Problem is, if a region of text that contains extmarks is changed...

Dammit :/ Could you post the output of `lua Luasnip_current_nodes[vim.api.nvim_get_current_buf()].parent:dump()` after changing the text in `$1`?

Yep, the problem is that the second node (`$1`) is in the range `(2,5), (2,9)`, whereas it should start at `(2,6)` (going after the text in your first screenshots). You...

Oh this is interesting, especially allowing different triggers to have different attributes (wordTrig, hidden). A simpler, although less versatile (but also complementary) idea would be to allow vim-regex as triggers....

Ahhhh now I get the `hidden`, I thought it was just an example to show that other parameters should also be accessible, but it was actually necessary for your usecase....

Ouh, do you have an example where deepcopy is necessary? I'm pretty sure not copying should work (and I'd like to make use of that in an eventual implementation), so...

Right, we do some initialization upon snippet-construction, not just on expansion :facepalm: Okay thank you, that would've made a few problems :D

Although just conceptually, it should be possible to make it work with just one copy of the snippet. I'll have to look into what exactly is causing the error