bug#61532: 30.0.50; [PATCH]: Make completions without sortText fall to back of the list

[Augusto Stoffel <arstoffel@gmail.com>]

On Sun, 19 Feb 2023 at 17:56, Stefan Monnier wrote:

>> Anyway, this boils down to a limitation of LSP, that it doesn't report on
>> what kind of matching style it uses for textDocument/completion.
>
> It's not just "matching style".  It's that it's designed under the
> premise that all the control is on the LSP server side, and the client
> (editor) side just provides a "dumb UI".

This not quite true, actually.  I once proposed a mechanism for the
server to request the editor to "act dumb", but the idea didn't stick.
Also, I gather from the discussion that VS Code does its own sorting and
filterting too.

https://github.com/microsoft/language-server-protocol/issues/898

> A better API is probably harder to design (e.g. you need to define what
> is a "matching style", for one), admittedly.

I think if the server returns all possible candidates with no filtering,
then Emacs would be happy, right?  Apparently some servers do that, as
claimed in the above discussion.  Of course there is one big issue with
this approach, namely the response can be quite big and slow down both
ends of the communication channel.