VSCode extension Clangd 0.1.7 stopped working when connecting remotely to host
See original GitHub issueSetup:
- VSCode version 1.49.1
- Clangd extension version: 0.1.7
- Remote-SSH extension version: 0.55.0
I am using the extension Remote-SSH to edit code on my office workstation (Linux) from my laptop (Windows 10). After updating the VSCode extension to version 0.1.7, whenever I start the editor I get this message:
The 'clangd' language server was not found on your PATH. Would you like to download and install clang 10.0.0?
It seems like the current version of the extension is not picking up the paths on the remote, because downgrading the Clangd version to 0.1.6 works fine.
These are the settings on my machines (both my laptop and office workstation) regarding clangd and terminal:
"clangd.path": "/compilers/linux-x86_64-2.10.1/clang9.0.0/bin/clangd",
"clangd.arguments": [
"--clang-tidy",
"--compile-commands-dir=lib/linux-x86_64-2.17/clang9.0",
"--log=verbose"
],
"remote.SSH.suppressWindowsSshWarning": true,
"terminal.integrated.shell.linux": "/bin/zsh",
"terminal.integrated.shellArgs.linux": ["-l", "-i"],
"terminal.integrated.cursorBlinking": true,
"terminal.integrated.copyOnSelection": true,
On the laptop (Windows) settings the entry “clangd.path” is a darker colour, probably meaning that it isn’t used. The paths used there (either relative or absolute) are the ones of the office workstation (Linux).
I have also tried killing/restarting the VSCode server but no luck.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:6
Top GitHub Comments
Had the same issue. Moving the setting to the remote config makes it work, but it is a bit confusing. Maybe some tooltip could guide the user if a non-standard path is present in the user config?
In vscode-clangd 0.1.7, we don’t respect the
clangd.path
in your local setting.json for remote mode.To keep it working, I think you’d need to put
"clangd.path": "/compilers/linux-x86_64-2.10.1/clang9.0.0/bin/clangd"
in remote setting (/usr/local/home/<user>/.vscode-server/data/Machine/settings.json
)