Wrong server selected about lsp-mode HOT 6 OPEN

I just came here to mention that I'm having a similar issue.

Given that I opened a graphql file instead of a TSX one when opening the project lsp mode suggested Graphql-lsp server (which is cool for the gql file), but whenever I open a tsx, it doesn't change the selected client, and I can't select it using +lsp/switch-client in doomemacs.

from lsp-mode.

Try to configuring the variable lsp-enabled-clients.

from lsp-mode.

Currently, that variable is empty, however, after manually installing the corresponding clients it apparently worked!

from lsp-mode.

Experiencing the exact same problem as OP here. vue-semantic-server is taking precedence over any other server when opening a file, even non-js-related ones. I noticed it only happens in workspaces where the vue server was used at least once, workspaces where I've not used it work normally. Working in multiple php+vue+typescript projects has made this a very annoying issue.

I'm using emacs-lsp in Doom Emacs on macOS although I was able to replicate the problem in a new emacs installation.

I can switch to the correct server (and/or client, not sure about the correct term here) using +lsp/switch-client in Doom to continue working so it seems that the problem is on file opening only.

from lsp-mode.

I'm having this issue in spacemacs.

Modifying lsp-enabled-clients is a silly solution. Whitelist all servers in order to blacklist one? I want to use vue-semantic-server in vue files. I must modify this variable every time I'm editing a vue app? What about when I'm working on a vue and react app simultaneously?

Is there no other way to manually switch an LSP client? I've been paging through google for about an hour and turned up nothing.

from lsp-mode.

M-x add-dir-local-variable with enabled/disabled clients should work.

from lsp-mode.