From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54488@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28?
Date: Wed, 23 Mar 2022 11:08:55 +0000 [thread overview]
Message-ID: <CALDnm52DnDyVQK0nYZmNiEhtWqRjrWkdBodff8e+rfboed-+8w@mail.gmail.com> (raw)
In-Reply-To: <87fsn9f07t.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On Wed, Mar 23, 2022 at 10:09 AM João Távora <joaotavora@gmail.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> PS: I do invite you to read that old Eglot issue. Since you're an
> expert on coding system conversion, maybe you know of a better, faster
> way to find the correct LSPish column in an Emacs buffer. Maybe the
> whole search idea is completely overwrought.
>
These issues may give additional context about the need for this particular
move-to-column dance.
https://github.com/joaotavora/eglot/issues/125 (the one I gave you already)
https://github.com/joaotavora/eglot/issues/124 (the bug that prompted the
125 fix)
https://github.com/joaotavora/eglot/issues/361 (an easier to grasp
manifestation of the problem)
Also, I think the current fix of Eglot is decent. It will be slower when
there are
company-mode overlays, but those are in much lower numbers compared to
LSP-abiding
positioning requests. And some seem to be moving away from company-mode
and its overlay-based completion display anyway. So this is not urgent.
But I still do think there was a regression in Emacs somewhere: I've
described an
unequivocal reproduction recipe, just not something that can be shared
among us,
due to technical (or licensing) hurdles.
João
[-- Attachment #2: Type: text/html, Size: 2032 bytes --]
next prev parent reply other threads:[~2022-03-23 11:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 6:54 bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28? João Távora
2022-03-21 12:32 ` Eli Zaretskii
2022-03-21 16:37 ` João Távora
2022-03-21 17:05 ` Eli Zaretskii
2022-03-21 21:59 ` João Távora
2022-03-21 23:14 ` Dmitry Gutov
2022-03-22 9:48 ` João Távora
2022-03-22 12:16 ` Eli Zaretskii
2022-03-22 13:57 ` Eli Zaretskii
2022-03-22 14:31 ` Eli Zaretskii
2022-03-22 14:54 ` João Távora
2022-03-22 15:22 ` Eli Zaretskii
2022-03-22 16:06 ` João Távora
2022-03-22 16:53 ` Eli Zaretskii
2022-03-22 21:05 ` João Távora
2022-03-22 23:55 ` Dmitry Gutov
2022-03-23 1:11 ` João Távora
2022-03-23 3:39 ` Eli Zaretskii
2022-03-23 10:10 ` João Távora
2022-03-23 11:08 ` João Távora [this message]
2022-03-23 14:21 ` Eli Zaretskii
2022-03-24 15:01 ` João Távora
2022-03-24 15:29 ` Eli Zaretskii
2022-03-24 16:03 ` João Távora
2022-03-24 16:59 ` Eli Zaretskii
2022-03-23 3:34 ` Eli Zaretskii
2022-03-23 3:29 ` Eli Zaretskii
2022-03-23 10:04 ` João Távora
2022-03-23 13:23 ` Eli Zaretskii
2022-03-24 14:54 ` João Távora
2022-03-22 12:33 ` Dmitry Gutov
2022-03-22 13:50 ` João Távora
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=CALDnm52DnDyVQK0nYZmNiEhtWqRjrWkdBodff8e+rfboed-+8w@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=54488@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
/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).