L3MON4D3

> > Might've been a bit hasty in asking for a PR sweat_smile What didn't work about just adding postfix to defaults? > > Maybe we could have an option...

Mhmm, I dislike a bit that `snip_env_extend`, a config option, controls the behaviour of another (though it is clear that they are related) I can see two other approaches: *...

So we'd expose `ls.config.with_default(user_conf)` and it extends the default.. Yeah that would work, but I think this isn't applicable to any other config-option, `snip_env` is the only one where we'd...

> IMHO either `snip_env` gets always merged with the defaults or we expose the defaults so the users do the merge themselves. Adding two parameters for the same thing seems...

We can (should I think, compatibility and all that) just replicate [these](https://github.com/microsoft/vscode/blob/71c221c532996c9976405f62bb888283c0cf6545/src/vs/editor/contrib/snippet/browser/snippetParser.ts#L372-L415)

Ouh, that might be due to unfortunate timing (coq/luasnip removing the same text seems likely atm).. could you insert a few (~20 should be more than enough) spaces (or any...

Yup, the idea is that we have no way of getting the captured text if the snippet is expanded via cmp. So, we expand an intermediary snippet where the variable...

> I apologize but I'm not able to follow this very well. So, in my/this case, I'd essentially have to trigger/expand the snippet twice? Yess :sweat_smile: > And by "captured...

> Hello, first of all, thanks for the most impressive snippet engine I ever used, period. :D I think the main problem here is that we don't make it _extremely_...

quick pr in #551, is it clearer this way? (Doc [here](https://github.com/L3MON4D3/LuaSnip/blob/fmt_doc_improve/DOC.md#fmt))