aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/_ftplugin
diff options
context:
space:
mode:
authorBartłomiej Maryńczak <marynczakbartlomiej@gmail.com>2025-04-26 16:08:03 +0200
committerGitHub <noreply@github.com>2025-04-26 07:08:03 -0700
commit83156974497df69a5f449c15d1fb472afdf7b6ff (patch)
tree1f8b606311a7ea9e3620e08173e27f6bc3a9cf00 /runtime/lua/vim/_ftplugin
parente45ec5a8527e155c2df68edd69c149f1342486a2 (diff)
downloadrneovim-83156974497df69a5f449c15d1fb472afdf7b6ff.tar.gz
rneovim-83156974497df69a5f449c15d1fb472afdf7b6ff.tar.bz2
rneovim-83156974497df69a5f449c15d1fb472afdf7b6ff.zip
fix(lsp): detect if Client:request resolved synchronously #33624
Problem: In cases when the (in-process) LSP server responds to the request immediately and calls `notify_reply_callback` the request will still be marked as pending, because the code assumes that the response will occur asynchronously. Then the request will be pending forever, because it was already set as "completed" before we even set it as "pending". A workaround is to wrap `notify_replay_callback` in `vim.shedule` ([like so](https://github.com/neovim/neovim/pull/24338#issuecomment-2809568617)] but that seems counterintuitive. Solution: Handle this case in Client:request().
Diffstat (limited to 'runtime/lua/vim/_ftplugin')
0 files changed, 0 insertions, 0 deletions