Shougo

> I don't think it's currently possible with nvim-cmp so this would be a feature request. Curious what you think. Hi. Why you cannot use `cmp.ConfirmBehavior.Replace`? It seems works for...

Hm.... If so, `MatchSuffix` behavior is to edit the suffix after insertion? And what is the cursor behavior after insertion when `MatchSuffix`?

Thanks. I get it. If so, this is feature request.

> The initial request is about having nvim-cmp recognize that the suffix helps disambiguate possible completions and having it select the resulting completion immediately without forcing the user to choose....

> In this instance Insert behavior would have done what I wanted, and MatchSuffix would have also; the line would contain "(KubernetesServices → Clusters → Data centers" and I'd just...

I think the cursor behavior is complex. > The cursor lands at the end of the matched suffix which I think is a good choice. If so, > With the...

> So what I'm proposing is more restrictive but if you chose a completion at some point, you can be sure the keyword isn't misspelled. It also feels less surprising....

Yes. It is @wincent 's idea.

> Here's a thought: To make Example A work, ConfirmBehavior.MatchSuffix could first try to perform a restrictive match on the suffix as I described above, and if it doesn't match...

https://github.com/hrsh7th/nvim-cmp/blob/d818fd0624205b34e14888358037fb6f5dc51234/lua/cmp/matcher.lua#L27 nvim-cmp uses case-sensitive as scoring.