How LSP could have been better
matklad.github.io
How LSP could have been better
1–10 of 229 posts
Re: How LSP could have been better
#2Re: How LSP could have been better
#3What the hell is LSP?
Re: How LSP could have been better
#4Re: How LSP could have been better
#5What the hell is LSP?
Re: How LSP could have been better
#6What the hell is LSP?
> The Language Server Protocol (LSP) defines the protocol used between an editor or IDE and a language server that provides language features like auto complete, go to definition, find all references etc.
Re: How LSP could have been better
#7https://github.com/joaotavora/eglot/discussions/1127
I don't know enough about emacs and LSP to see the full picture, but it seems that both eglot's and corfu's maintainers, assumably very competent programmers, can't find a solution for this.
I only skimmed the thread. My understanding is that LSP dumps a long list of completion candidates at once and they can't decide a cache strategy that works well with existing code...? If someone who know more about this please enlighten us.
Re: How LSP could have been better
#8Does anyone know why LSP uses UTF-16 for encoding columns? It seems like everyone agrees it is a bad choice, so I'm curious about the original reasoning. Are there any benefits at all to using UTF-16, or was it something to do with Microsoft legacy code?
Re: How LSP could have been better
#9What the hell is LSP?
https://en.wikipedia.org/wiki/List_of_Adventure_Time_charact...
Re: How LSP could have been better
#10Does anyone know why LSP uses UTF-16 for encoding columns? It seems like everyone agrees it is a bad choice, so I'm curious about the original reasoning. Are there any benefits at all to using UTF-16, or was it something to do with Microsoft legacy code?
[1] https://github.com/microsoft/language-server-protocol/issues...