I'm a go user myself and I know what that means

Sorry, I thought you just owned a plush gopher, not that you were a gopher, have to watch out you don't start Goany. So leaving testing gopls to you. 😁

Ahem, anyway back to LSPs.

Basically we seem to be in vociferous agreement, but from differing points of view.

Your "isn't a "correct" name in the sense of TM" is my "LSP servers don't give incorrect symbols like TM/ctags".

I for instance don't know what plugins could do with calls like autocompletion or goto tag definition.

Agreed, no point in trying to use LSP symbols to do what LSPs themselves do (and if one server doesn't do it, don't use that LSP server, use TM/ctags unLSP "server").

I just mentioned it because the current interface is of this kind already, only the implementation supports a single plugin, but that could be changed easily.

Baby steps, we mustn't let @b4n suspect we are moving all of Geany into per language plugins 😉

The only thing we can do is display them as they are without trying to "understand them", because we can't.

The only alternative is to have per server LSP clients that understand the servers replies and can interpret them sensibly. That would be part of the per language plugin. So for now best to do nothing but show them.

On the topic, the paragraph setting is helpful, the per line one tended to cut stuff off if it happened to be a bit long. But for pylsp the paragraph setting would be best as 1 and clangd 2 AFAICT, so maybe later it can be per server.

Also you said that per project LSP settings were possible, but didn't say how to set that up.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.