L3MON4D3

I used the one from `friendly-snippets`, im assuming you're talking about that one. If not, please post the snippet so I can try it.

Dammit, could you try the snippet in other filetypes eg. `:lua require("luasnip").snippets = {all={require("luasnip").parser.parse_snippet("for", "for ${1:i} := ${2:0}; $1 < ${3:count}; $1${4:++} {\n\t$0\n}")}}` and see if it still misbehaves?

I'm on `NVIM v0.6.0-dev+181-g5d633546b` (current master), maybe try updating and see if that fixes anything

Do you still experience the issue?

Could you post the output of `:lua Luasnip_current_nodes[vim.api.nvim_get_current_buf()].parent:dump()` directly after expanding the snippet and after jumping?

Okay, the extmarks are getting messed up pretty bad, does the issue also occur if you expand manually?

> To save Oh, does it not occur if you just jump to the next node?

Seems like it :/ My only explaination would be another plugin interfering.

Mhm, yeah that's probably more intuitive than the current behaviour. (This specific setup is even possible currently, but only if each snippet is "jumped through" completely) We only have to...

Oh, no, I think it's possible to implement your idea :D Just wanted to highlight that it depends on where the new snippet is expanded (before/inside/behind the old snippet)