unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 72824@debbugs.gnu.org
Subject: bug#72824: Eglot highlights matches incorrectly wrt case sensitivity
Date: Wed, 28 Aug 2024 10:03:58 +0100	[thread overview]
Message-ID: <CALDnm50o83nHme=qAFB6pDvFdVRi_16jqXNrbMLEobwvGO8s5A@mail.gmail.com> (raw)
In-Reply-To: <7cf49afe-e52f-471c-942d-72a0a39d0905@gutov.dev>

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.

> 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.  These users are continuously
misinformed  about LSP inability to follow Emacs's completion styles,
despite my frequent admonishing.

João Távora





  reply	other threads:[~2024-08-28  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  1:38 bug#72824: Eglot highlights matches incorrectly wrt case sensitivity Dmitry Gutov
2024-08-27 14:36 ` João Távora
2024-08-27 14:38   ` João Távora
2024-08-27 22:57     ` Dmitry Gutov
2024-08-28  9:03       ` João Távora [this message]
2024-08-28 21:20         ` Dmitry Gutov
2024-08-27 23:23   ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALDnm50o83nHme=qAFB6pDvFdVRi_16jqXNrbMLEobwvGO8s5A@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=72824@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).