Hi, Am Sonntag, dem 02.01.2022 um 10:59 +0100 schrieb antonio: > > > > I'm not sure about the comment for cnd-small/3: > > > > The cpplite.editor indeed builds on top of the lsp.client module. The > > class org.netbeans.modules.cpplite.editor.lsp.LanguageServerImpl is the > > binding between the configuration, that the cpplite.editor module > > provides and the LSP API, that is provided by lsp.client. If I read the > > code correctly, ccls is used, if configured and switches over to clangd > > else. > > Yep. I have to rephrase that. cpplite does indeed use lsp.client. The > user interface is somehow duplicated, though: > > - lsp.client has a panel (Editors/Language Servers) in the Options Panel > where language servers are registered. > > - cpplite has instead a C/C++ top-level tab in the Options Panel, where > it automatically checks for ccls and clangd in the PATH. That's very > handy. But not clangd nor ccls are registered in the panel in lsp.client.
in my mind, this is not that bad. The LSP specific dialog is for servers without direct support in NetBeans. C/C++ support is different in, that it directly supports two different LSP servers. Consider TypeScript in that case we even carry the whole infrastructure (apart from the node runtime). While a unified approach might be helpful, I would not put too much focus on that and first focus on getting the rest working. To me this sounds like polishing. Greetings Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
