Chicken-or-the-egg problem with LSP
My Python LSP server is installed in the virtualenv that auto-virtualenv is activating.
When opening a Python file LSP tries to start a server for it before auto-virtualenv activates for that buffer and fails. When auto-virtualenv finishes activating, it tries to reload the LSP server with lsp-restart-workspace but that doesn't do a reload because "lsp-restart-workspace: There are no active servers in the current buffer".
Is there a way to get these ordered properly?
Hi @alamaison,
Could you check the Messages buffer to see what it says?
Do you have auto-virtualenv-verbose set to t?
lsp-restart-workspace has been changed to lsp-workspace-restart
Hi @chrisemke i am not sure i understand what you meant?