I guess kakoune under WSL can be a good solution if we would like to use it under Windows.
Kakoune version has been installed with the git clone
$ kak -version
WSL Ubuntu version is
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Clangd version installed with apt-get is
$ clangd --version
clangd version 7.0.0-3~ubuntu0.18.04.1 (tags/RELEASE_700/final)
kak-lsp can be launch
Apr 19 10:50:19.208 INFO Starting main event loop, module: kak_lsp::session:31
Apr 19 10:50:19.209 INFO Starting editor transport on 127.0.0.1:31337, module: kak_lsp::editor_transport:106
Debug buffer of kakoune
*** This is the debug buffer, where debug info will be written ***
Dependency unmet: gocode, please install it to use go-tools
Dependency unmet: goimports, please install it to use go-tools
Dependency unmet: gogetdoc, please install it to use go-tools
Dependency unmet: jq, please install it to use go-tools
and kak-lsp.toml has been modified and moved from .config/kak/plugins/kak-lsp/ to .config/kak-lsp/
But when I launch a “.cpp” with Kakoune, I don’t see kak-lsp activation.
I should see the error code activation on the number line column.
And other clangd functionnality.
Other strange behaviour is that I can not see the kakoune command :ranger ??
Hello! It might worth trying to run kak-lsp server manually with debug logging for better understanding of the problem.
Try to do kak-lsp -s mysession -vvv in one terminal, and open file inside your cpp project with kak -s mysession src/path/to/my/file.cpp afterwards in another one. Debug output in the first terminal could have clues for goes wrong.