Closed mathjiajia closed 2 years ago
I think this is a nice idea for users that prefer separate mappings for jumping between tabstops and selecting the next completion item. Still, I would argue that expand_or_jump_forward
should be the default for new users since it feels intuitive. Would you agree? I think I will add this later (but the readme will also have to be updated).
I would argue that expand_or_jump_forward should be the default for new users since it feels intuitive
I feel good 👍 let's do it
I think this is a nice idea for users that prefer separate mappings for jumping between tabstops and selecting the next completion item. Still, I would argue that
expand_or_jump_forward
should be the default for new users since it feels intuitive. Would you agree? I think I will add this later (but the readme will also have to be updated).
Thank you.
Once #48 is merged (soon), you can achieve your desired behaviour like this:
["<Tab>"] = cmp.mapping(
function(fallback)
cmp_ultisnips_mappings.compose({ "expand", "select_next_item" })(fallback)
end,
{ "i", "s", [[ "c" to enable the mapping in command mode ]] }
),
["<S-Tab>"] = cmp.mapping(
function(fallback)
cmp_ultisnips_mappings.compose({ "select_prev_item" })(fallback)
end,
{ "i", "s", [[ "c" to enable the mapping in command mode ]] }
)
Thank you so much. That looks great!
Hi, thanks for this fantastic plugin.
Since I do not want to integrate too many functions in the
Tab
key. Actually , I use the default jump key ofUltiSnips
, which isC+J
. Could you add a new functionexpand(fallback)
.Something like below:
Thanks