Benoit de Chezelles
Benoit de Chezelles
👍 Does that mean that we could theoretically dynamically add/remove surrounds that will then be available when triggering surround actions?
Your second example made me think about a nice history thing [I configured in zsh](https://github.com/bew/dotfiles/blob/a9eb916173a7c42b4bcb41e1ee2916b1b6f4f67c/zsh/rc/completions.zsh#L323-L328) and I use a lot: `words history` It basically allows me to complete any words...
> Also, does this seem tractable for a first contribution to you? If so, I would appreciate some guidance as to where this special casing should be taking place in...
note: I actually noticed that using `has_selected_text` from the extra show conditions module _always_ returns `false` when inside a snippet for some reason. If I instead check that `snip.env.LS_SELECT_RAW` isn't...
fyi: With the rework of how selection/restore works from #1013 (last year), the way to check for this is now: ACTUALLY THIS IS WRONG (see below) ```lua function has_stored_selection() local...
Actually the code I posted above is wrong 👀😬. Since the luasnip impl will retrieve the selection from buffer vars and immediately after clear those variable, it's no longer possible...
On the topic of breaking changes, it could be a new Lua API only, without default keybind 🤔
Related #378 (but incomplete)
In #1117 (and https://github.com/L3MON4D3/LuaSnip/pull/1117#issuecomment-1943633183) we saw that type hinting the nodes is tricky because of the lazyness of `ls` table. /cc @michaeldebetaz Now that I played with types a lot...
> Any updates on this? It would be amazing if you could actually have some docs/type completion for the various methods. I opened #1318 with the base idea I mentioned...