Lucas Alber

Can you check if there is an error in the LSP Log Panel? You can open the panel by executing the command `LSP: Toggle Log Panel`

@rchl Do you have an idea?

Do you talk about the diagnostics panel or the status bar?

I have one for LSP-clangd too https://github.com/sublimelsp/LSP-clangd/blob/main/.github/workflows/update_check.yaml

Can you give more info please? Minimal example, config and logs.

Sounds like an issue with your clangd installation in `/usr/bin`.

That may be caused by ST reloading the plugins (in the wrong order?)

The issue is reproducible: Console log: ``` LSP: starting ['D:\\Local_Repositories\\windows-dev-tools\\bins\\node\\node.EXE', 'C:\\Users\\Lucas Alber\\AppData\\Local\\Sublime Text\\Package Storage\\LSP-json\\15.8.0\\language-server\\node_modules\\vscode-json-languageserver\\out\\node\\jsonServerMain.js', '--stdio'] in C:\Program Files\Sublime Text reloading settings Packages/User/LSP-TexLab.sublime-settings LSP: applying .sublime-project override for LSP-TexLab LSP: applying...

Forward search is unbound. You must set up a key bind executing the command `lsp_texlab_forward_search`.

From this comment I understand that it does not work in VS code, meaning ST behaves the same? > I tired to see how the Biome extension behaves in VS...