>> On the other hand, if we follow-up on your other idea and use LSP even to >> interface with the ctags parsers then documentSymbol ought to be sufficient >> for all existing features (except maybe where we can specialized LSP >> interfaces like goto-implementation), right?
> I was thinking about it and not to lose functionality, I think we'd have to > introduce some Geany-specific members like _geany_var_type. It sucks a bit > and I haven't checked the LSP specification in detail if it explicitly > prohibits something like that but I think even with extra members we should > be LSP-compliant. So I'm forgetting about how LSP works myself too :-). No, you won't need anything extra. Basically, we only need things like `var_type` or `arglist` for autocompletion or calltips, respectively, and these will be only needed on the server for the autocompletion or signature calls, but not on the client side any more. So `detail` could contain whatever we need to show in the calltip in the symbol tree. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3571#issuecomment-1795800132 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/3571/c1795800...@github.com>
