Yi Ming 6f733f4a9b 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.

2026-02-03 09:33:14 -05:00

..

nvim

refactor(lua): use vim.fs instead of fnamemodify

2026-01-28 10:57:39 +00:00

uv

build(deps): bump luv to 1.51.0-2

2026-01-23 09:30:37 +01:00

vim

fix(lsp): avoid scheduling client deletion before LspNotify #37685

2026-02-03 09:33:14 -05:00

coxpcall.lua

build: add luals check

2025-02-09 18:10:54 +01:00

editorconfig.lua

docs: misc, editorconfig

2025-12-15 13:55:15 -05:00

man.lua

refactor(lua): use vim.fs instead of fnamemodify

2026-01-28 10:57:39 +00:00

tohtml.lua

feat(tui): add nvim_ui_send (#35406)

2025-08-22 15:05:43 -05:00