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

[Stefan Monnier]

> 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".

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

> At least it used to be a limitation of LSP, maybe someone else has
> fixed it in the meantime, or added something that we can use.

Not that I know.  But I think if we want that to happen, we need to move
out of our comfort zone and start participating in discussions over in
VScode land where the decisions are made :-(


        Stefan