You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
simply made _notify_workspace_folder_added return a boolean it will cause another prolem vsplit open two file which in two projects and mksession then nvim -S Session.vim print existing_client.initialized it will be nil when second buffer attached . that mean we can not get the
server_capabilities at that time reuse_client will return false. before use a timer to wait first server initialized then check it support workspacFolder or not . refactor mentioned add in new_config hook that doesn't make sense.
The text was updated successfully, but these errors were encountered:
Is this the successor to #3456? I'm also having an issue where multiple vtsls servers attach to a buffer upon open.
From my investigation, the issue is repeated (programmatic) calls to vim.cmd.LspStart (by a plugin). Previously, they seemed to be idempotent, but now more LSPs are started with each call to :LspStart.
I ran a bisect:
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
8d9fd3581ac07a2e1940435e13bda31a0cdeb795 (this commit does not run for me at all, it gives a long error)
2eccb418f2f972ad1167f8491a8180acdeb02384
Description
tsserver does not support workspaceFolders, even the server does not support workspaceFolder it still return true.
nvim-lspconfig/lua/lspconfig/manager.lua
Lines 134 to 145 in 064221e
simply made
_notify_workspace_folder_added
return a boolean it will cause another prolem vsplit open two file which in two projects and mksession thennvim -S Session.vim
printexisting_client.initialized
it will be nil when second buffer attached . that mean we can not get theserver_capabilities at that time reuse_client will return false. before use a timer to wait first server initialized then check it support workspacFolder or not . refactor mentioned add in new_config hook that doesn't make sense.
The text was updated successfully, but these errors were encountered: