Open ItsHoff opened 2 years ago
That is a known limitation, we should restructure lsp-mode to pick project root before checking if there is server matching the current file.
@yyoncho Is there a workaround for this limitation ?
@dirodriguezm the workaround is in the report description - use lsp-workspace-folders-add before opening the project
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
Volar language server does not start for a fresh Vue project.
Steps to reproduce
npm init vue@latest
Expected behavior
Volar server is started, or Volar offered in the list of servers that can be installed.
Which Language Server did you use?
lsp-volar
OS
Windows
Error callstack
Anything else?
It seems that
lsp-volar--activate-p
expects to findlsp-workspace-root
(https://github.com/emacs-lsp/lsp-mode/blob/358b5df8df10b4837193af78c2e72df2c381b1fa/clients/lsp-volar.el#L118-L128), which in this case isnil
. If the project root is added usinglsp-workspace-folders-add
then Volar starts as expected.