L3MON4D3

Ahh, 346 is just the number of `add_snippets`-calls, not the number of snippets :facepalm: Okay that makes more sense :+1: `get_snippets` is pretty much always used from `cmp_luasnip`. It would...

I don't understand what the benchmark is supposed to do :sweat_smile: Wouldn't a simple `get_snippets("")` do it? (maybe repeated to actually see the differences) > (Remark: get_id_snippet didn't always returned...

You're doing nothing wrong, it just isn't supported yet. > If is not a feature yet, could it be someday? definitely :D

soooooooooooooooooooooo, with the current master it should work automatically for snippets loaded via `loaders.from_snipmate`. `ls.parser.parse_snipmate` can be used otherwise.

> Sadly nvim does not expose a way to get the matches of the regex, only the full match. So if we wanna make it, a PR to nvim will...

> Currently `regex:match_str({str}` returns a tuple with the position of the full match, and that does not allow passing the matched groups. Adding that API to nvim should be an...

Uuhm yeah, why not👍 Currently we simulate the captures as Variables for lambda (`l.CAPTUREn`), it might be nice to remove this special handling in lambda and just let `CAPTUREn` resolve...

> It would be better if `parse_snipmate` could also support this! If it's supported in one, it'll also work in the other :D Right now they use the same parser,...

> Well, there is a way around we don't allow namespaces starting with `_` because of a limitation of the old parser (I added an assert intentionally smile) so we...

Yes, that could very well be related to luasnip+formatting. Could you do `:lua Luasnip_current_nodes[vim.api.nvim_get_current_buf()].parent:dump()` (prints the nodes' positions) after the text was duplicated? I'd assume the extmarks get messed up...