Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@techee how are you proposing to handle dependency information for the LSP? It needs to know where to find include files for C++ for example so it can perform complete type tracing. Geany does not have that information available ATM, and heavyweight IDEs do it by parsing the build system, makefiles, meson files, cmake files etc.
By using an external tool, independently from Geany since Geany itself doesn't know how to build projects and relies on external tools already. I don't know if you had time to play with the plugin and if you checked
https://github.com/techee/geany-lsp/blob/master/README.md
but for clangd, it uses the build_commands.json generated by meson. I also tried to use the Bear tool with our autotools build and it works too.
Other languages may/may not need something similar. With the python pylsp server and the go gopls server nothing like that seemed to be necessary.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.