L3MON4D3

Oh wow, thank you, that's great to hear :D Don't worry about noobishness (and waiting periods especially, we're all doing this in our free time, some have more, some less),...

I think we're inserting a [copy](https://github.com/L3MON4D3/LuaSnip/blob/6e10a30178240182781955ce062618c8d793a37b/lua/luasnip/extras/fmt.lua#L94-L102).

In this case yes, we could probably implement that as well, but I'm not sure it's the right thing to do: `fmt` is very simple and easy to reason about...

Reusing keys is allowed (okay they're copied which doesn't do much, I agree), what `fmt` does not do is generate new nodes. But that being your assumption is good to...

Okay, also bad wording on my part, "new nodes" -> "different nodes". We could probably introduce duplicate->repeat-node as a setting for `fmt` (though it'll default to off since I'm not...

> I wasted a couple of minutes until I decided this was maybe a bug in LuaSnip, thankfully I didn't invested a couple of hours :stuck_out_tongue_closed_eyes:! :sweat_smile: > IMO the...

Hmm yeah, that would work :+1: It might be best to provide these behaviours separately though, so * one option for number-key -> `i(num)` (`{}` are also numbered indices behind...

> Maybe I missed this in the previous discussion, but how are we gonna get the node_index which shall be repeated (as node_index != index in the fmt table) without...

> +1 The advantege I see over `parse` is that this way you can mix different kinds e.g. `("{user}: hello {world}", {user=functionNode(...)}`, where `user` could be a function node resulting...

Oh wow, that's awesome! Thank you for dedicating so much of your time to explaining Luasnip❤️ I'm looking forward to the next parts :D (especially the intro, this one was...