[vim/vim] Omnicomplete regression? (Discussion #19498)

[Gabriel]

since update to gvim-9.2.0038-1-x86_64 on archlinux, omnicomplete now shows up by default while typing (exactly as described in #19308 --it didn't before) and then hangs forever (exactly as described in #4493 ).

process tree looks like

gvim,56064 src/file.ts
  ├─node-MainThread,56107 ./node_modules/.bin/tsserver
  │   ├─node-MainThread,56137 ./node_modules/typescript/lib/typingsInstaller.js --globalTypingsCacheLocation ~/.cache/typescript/5.8 --typesMapLocation...
  │   │   ├─{node-MainThread},56138
  │   │   ├─{node-MainThread},56139
  │   │   ├─{node-MainThread},56140
  │   │   ├─{node-MainThread},56141
  │   │   ├─{node-MainThread},56142
  │   │   └─{node-MainThread},56147
  │   ├─{node-MainThread},56122
  │   ├─{node-MainThread},56123
  │   ├─{node-MainThread},56124
  │   ├─{node-MainThread},56125
  │   ├─{node-MainThread},56126
  │   ├─{node-MainThread},56134
  │   ├─{node-MainThread},56149
  │   ├─{node-MainThread},56150
  │   ├─{node-MainThread},56151
  │   └─{node-MainThread},56152
  ├─{gvim},56065
  ├─{gvim},56066
  ├─{gvim},56067
  ├─{gvim},56069
  ├─{gvim},56070
  ├─{gvim},56071
  ├─{gvim},56072
  └─{gvim},56110

Killing the underlying LSP process does not restore vim to a functional state.

also happens with backspace= (originally had set backspace=eol,start,indent)

starting gvim -f will cause the problem to happens in different places? (or i am just going crazy). But more importantly, I can recover the session just fine with ^C. If running without foreground, i must kill vim.

I can compare with VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Oct 21 2025 14:27:36) which I have compiled from source when trying to debug something else here, and none of this happens (i must manually invoke omnicomplete, and when i invoke it, it doesn't crash anything)

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/repo-discussions/19498@github.com>

[Gabriel]

and since i adopted the gvim -f+^C workaround to finish some work... i've been doing that a lot, and noticed sometimes when i ^C on the terminal, the omnicomplete window shows up on vim with the correct expected contents!

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/repo-discussions/19498/comments/15917268@github.com>