L3MON4D3

Yes that's the correct one :D :facepalm: Normally these indices should be consecutive, here the marks are getting moved around. Sadly there's little we can do about that (except manually...

That looks correct, you can see that all nodes are adjacent (`(3,0)->(3,9), (3,9)->(3,11),...`), which is the correct behaviour. I guess efm does something nicer, eg. not formatting at all or...

> I have to place them in completely different parts of the document, since they have to be returned in 2 separate tables, which feels kind of clunky > feel...

Right that would work... though I'm not sure the current approach needs to be removed, I don't think the implementation would need to be much more complicated to support both

Oh, no I have not :sweat_smile: I'm pretty busy right now, and there's other luasnip-related stuff I wanna get to before this, so you're very welcome to get on this...

Setting tests up should (:grimacing: xD) be as straightforward as running `make test`, let me know if it's more involved than this, maybe I can make it easier. But this...

Oh, I'm in favor of adding this in `snippet_collection`, the `add_snippets` in `init.lua` is (in my mind :sweat_smile:) more for providing a slightly more ergonomic interface to `snippet_collection` (and to...

> Oh of course (maybe, write a comment then with what function serves what purpose to make it clear when someone reads the code base). Yes, some parts are severly...

> Yes knowing the structure (all the `by_...` tables) in which the snippet has to be stored, I think it is readable. Okay, nice :) > > snip.autotriggered may not...

> Why not. But 3 values, `-1 = unset`, `1 = set to true`, `0 = set to false` should be enough (just an example mapping). I see no need...