completions inserted strangely when trigger.completion.keyword_range = "full"

[stefanboca]

Make sure you have done the following

• I have updated to the latest version of blink.cmp
• I have read the README

Bug Description

Screencast.From.2024-11-04.22-51-32.mp4

When keyword_range = "full", inserting a completions from the middle of a word duplicates the last character if the last character is the end of the phrase. The ghost text is also incorrect (it appears a few characters after the cursor).

Screencast.From.2024-11-04.22-58-43.mp4

This does not occur when there is no space after the current word.

Screencast.From.2024-11-04.23-00-58.mp4

Additionally, when keyword_range = "full" I noticed that if the cursor is in the middle of the word, and the second half doesn't match any completions, no completions are displayed (even if manually triggered). I'm sure this is a tricky edge case, but I would prefer the behavior to fallback to normal completions in this case.

Relevant configuration

trigger = {
  completion = {
    keyword_range = "full"
  }
}

neovim version

NVIM v0.11.0-dev+1090-g99acc9de5 Build type: RelWithDebInfo LuaJIT 2.1.1720049189

blink.cmp version: branch, tag, or commit

main (1628800)

[stefanboca]

I actually just checked to see if this still happens after #389 (and it does), but I noticed this actually looks like a matching issue:

You can see the last r is not being matched.