When accepting a word, the virtual text should be kept.

[gaoqiangks]

I set <tab> to accept_word

keymap = {
accept = "<M-w>",
accept_word = "<Tab>",
accept_line = false,
next = "<M-]>",
prev = "<M-[>",
dismiss = "<C-]>",
},

However, when a word is accepted, the virtual text is cleared, and after 1 or 2 seconds, the virtual text appeared again. However, when I accept a word, the text generated by Copilot is more likely to be the same with what they it was before it is clear. Therefore, I think the virtual text should be kept. Here's a video shows what vscode does.

20250420_171856.mp4

It's usually that I don't want to accept all the things copilot generated, but just some words. In vscode, I can use <tab> <tab> <tab>... until what I decide to write something by myself.

[AntoineGS]

Yeah that would be a good improvement, I will look into it!

[GitMurf]

@AntoineGS I am not sure if these changes were the cause but I just noticed in the last day or so a weird behavior where if I am typing and ghost text appears for a copilot suggestion, it sort of "stutters" as if it is resetting the completion and virtual text. In the past I could type and it would just smoothly type "over" the suggested virtual text unless I started typing something different than the virtual text at which point it would correctly give a new suggestion.

The TLDR I believe is that we should not re-trigger the completion and/or not reset the virtual text if the suggestion is the same and still valid because you are typing the same thing that copilot has suggestion currently.

Here is a video showing what I mean:

WindowsTerminal.-.Arch_CbVJKDHonP_2025-04-23_10-33-23.mp4

Let me know if you have any questions.

[GitMurf]

If I change the debounce to 1000 you will see a different problem which it just keeps pushing the virtual text to the side which never happened in the past. So now that I think about it a bit more, I think potentially in the past it just got rid of the virtual text on keystroke and the change related to this gh issue meant to keep the ghost text around when accepting the "next word suggestion" (which I do like by the way) is causing a problem here.

WindowsTerminal.-.Arch_2HoGzQ1XBL_2025-04-23_10-38-59.mp4

[GitMurf]

See issue #471 I just opened...