diff options
| author | Yi Ming <ofseed@foxmail.com> | 2026-02-03 22:33:14 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-02-03 09:33:14 -0500 |
| commit | 6f733f4a9bf01d40235774e553f193facc33945f (patch) | |
| tree | 891325cd5111ef13ebebd268e47cb84e3c77d6eb /test/functional/vimscript/executable_spec.lua | |
| parent | 16680e57bacadbf2b0493e89f5f62e9fb1b69328 (diff) | |
| download | rneovim-6f733f4a9bf01d40235774e553f193facc33945f.tar.gz rneovim-6f733f4a9bf01d40235774e553f193facc33945f.tar.bz2 rneovim-6f733f4a9bf01d40235774e553f193facc33945f.zip | |
fix(lsp): avoid scheduling client deletion before LspNotify #37685
Problem:
`Client.on_exit` runs `Client._on_detach` and the client removal logic
within two separate `vim.schedule` sequentially. However, since
`Client._on_detach` executes `LspNotify` inside `vim.schedule`, this
causes `LspNotify` to be executed after the client removal, which is
scheduled first. At that point, a valid `Client` can no longer be
retrieved within the autocmd callback.
Solution:
Put the client deletion inside the `vim.schedule` call.
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions