Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Why does cmd must be absolute path to clangd? I have clangd binary in PATH and other LSP Client are fine with that.
Maybe it's not necessary, you have to try (if the plugin doesn't find clangd, you get corresponding messages in the Status tab).
As it seems the plugin didn't even attempt to start clangd in your case, I suspect you didn't enable the plugin for your project in step (5) of https://github.com/techee/geany-lsp?tab=readme-ov-file#quick-start
BTW, how does this absolute path look like? Forward slashes C:/clangd_19.1.2/bin/clangd? Normal backward slashes C:\clangd_19.1.2\bin\clangd? Double backward slashes (UNC) C:\clangd_19.1.2\bin\clangd? Is the extension .exe needed?
I think both forward slashes / and double backward slashes \\ work. Not sure about exe, I think it doesn't matter.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.