L3MON4D3

Yeah, this issue can't happen with the default `choiceNode`-approach for nesting placeholders, which is one reason for having this in the wiki and not in luasnip. If I have time...

I think (hope, at least linux is capable of this afaik) the lines should stay intact, but they will be interleaved for sure. I've considered prepending a unique identifier for...

(Quick test confirms my hope :D) [luasnip.log](https://github.com/L3MON4D3/LuaSnip/files/9501098/luasnip.log)

Ouh, looks like the content of `plugin/snip.lua` depends on the `l` from the default-table. The defaults are currently not exported (and I'm not sure we want to do so), but...

> Want to add postfix to setup_env, could this be default? Do a PR, I'll add it :P

Mhmm, I don't know, some users don't like/use the `i`, `s`, single letter-acronyms for the nodes, and I wouldn't like to force those on them. Maybe we should expose the...

"force" is maybe a bit strong, more like have these globals defined when they are not used at all.

xD Mhmm ahhhh yeaaaaahh... I'm not sure, on the one hand, we override default-stuff when a custom-table is assigned to `snip_env`, local variables will also override the defaults, so everything...

Might've been a bit hasty in asking for a PR :sweat_smile: What didn't work about just adding postfix to defaults?

> @L3MON4D3 Will have following errors:  Ahh, changing `local snip = require("luasnip").snippet` to `local snip = require("luasnip.nodes.snippet").S` in `postfix.lua` should fix that