[vim/vim] Exiting insert mode before `autocompletedelay` spams `KE_COMPLETE_DELAY` (Issue #20737)

[sev]

sevmonster created an issue (vim/vim#20737)

Steps to reproduce

1. Start vim with -u NONE
2. Run :set autocomplete autocompletedelay=1000
3. Start insert mode, type something, and exit insert mode before the delay ends
4. Start, for example, command-line mode

You can observe the command-line will have <t_<fd>n> repeated every &autocompletedelay milliseconds. This cannot be stopped as far as I can see, even if you set noautocomplete. Changing autocompletedelay changes how fast the escape sequence is written, even after triggering the bug, and entering/exiting any mode. I can tell too that the sequence is being sent even when in normal mode, since my terminal dings when the sequence is sent.

For verbose reference, the escape sequence K_SPECIAL KS_EXTRA KE_COMPLETE_DELAY is represented in Vim as <t_<fd>n>.

Expected behaviour

The escape sequence isn't written in command-line mode, and isn't sent repeatedly when it can't be sent/received properly.

Version of Vim

9.2.747

Environment

Happens over SSH when SSHing into my Alpine Linux x86-64 box, from the following terminal hosts:

• Termux 0.119.0-beta.3 on latest GrapheneOS
• Windows Terminal app on Windows 11
• Windows legacy console host (conhost.exe) on Windows 11

I've been unable to reproduce in Termux executing Vim directly, with Vim version 9.1.2100. I am thinking maybe SSH is required to reproduce, or it's a newer regression. I'll try on more devices later.

Logs and stack traces

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/20737@github.com>

[zeertzjq]

zeertzjq left a comment (vim/vim#20737)

I think this is already fixed by patch 9.2.0750

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/20737/4920320471@github.com>

[gobobopawa]

gobobopawa left a comment (vim/vim#20737)

7e8c23937cc74b2259f75d4b.zip
not sure if it's your case though

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/20737/4920332963@github.com>

[sev]

sevmonster left a comment (vim/vim#20737)

This? If so, thanks, I missed it somehow.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/20737/4920377181@github.com>

[h_east]

h-east left a comment (vim/vim#20737)

Yes, I introduced that bug in version 9.2.0739.
As he mentioned, it has been fixed in version 9.2.0750.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/20737/4921317208@github.com>