bug#72824: Eglot highlights matches incorrectly wrt case sensitivity

[Dmitry Gutov <dmitry@gutov.dev>]

On 28/08/2024 12:03, João Távora wrote:
> On Tue, Aug 27, 2024 at 11:57 PM Dmitry Gutov <dmitry@gutov.dev> wrote:
> 
>> This change should help eliminate the inconsistency between parts of the
>> current completion style, but for the next release we might migrate to a
>> more "passthrough" one.
> 
> What's that?  Modulo bugs (one of which you've fixed recently) the "dumb"
> is the most passthrough one, except for the completion-ignore-case.
> Do you want to remove that?  I added it at some user request... seemed
> reasonable.  Maybe it's not.

"dumb" does some filtering in its all-completion call (the predicate arg 
is used for its return value, AFAICT).

A "passthrough" style would only add highlighting but not filter.

>> Or not, you know. I've seen users request prefix-only matching instead
>> of the fuzzy one provided by the language servers, and I'm sure there
>> will be ones who prefer to match case-sensitively only too.
> 
> There is no way to do that.  We don't have a say in what the server
> gives us.  If the user types foo and the server ignores "foobar" and
> prefers "farfromsober" or std::foobar for whatever scoring reason, then
> there's nothing we can do about it.

I suppose that can happen if total completions exceed the cutoff number.

> These users are continuously
> misinformed  about LSP inability to follow Emacs's completion styles,
> despite my frequent admonishing.
My observation from the sidelines is that people are still happier to 
have such half-measures available, rather than not: 
https://github.com/emacs-lsp/lsp-mode/issues/1653#issuecomment-1125055989

It might be a matter of expectations.