-
|
I love how I can still navigate through nodes of the snippet even after returning to it later. However, it's frustrating when Is it possible to achieve this:
If not, could you suggest a best-effort setup? Should I disable the related settings altogether, not to hinder Here is my current setup. To be honest, I have only a remote idea what these settings do, since I can't confidently map them to require("luasnip").setup({
keep_roots = true,
link_roots = true,
link_children = true,
exit_roots = false,
update_events = { "TextChanged", "TextChangedI" },
ext_opts = {
[require("luasnip.util.types").choiceNode] = {
active = {
hl_group = "LuasnipNodeActive",
},
},
},
})Thank you! And sorry if this was answered before, or if there is a direct solution within help files. For some reason, I can't find it, or can't grasp key concepts. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Hi :) I think for this I'd set
And then bind This is off the top of my head, but I think conceptually it may be a good fit :) |
Beta Was this translation helpful? Give feedback.
Okay, so it seems I have two options for now:
(1) changing blink.cmp config to:
(2) adding this to luasnip config:
The second one is stricter. It deactivates even the most recent snippet once I enter insert mode outside its bounds. I will stick to the first one f…