unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 21 Mar 2022 16:37:18 +0000	[thread overview]
Message-ID: <CALDnm53Wb9v1qRSB2RX_uKqB6=hrNi2+8aOnCyNRfHJ1BnX7sg@mail.gmail.com> (raw)
In-Reply-To: <831qyvfpv4.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On Mon, Mar 21, 2022 at 12:32 PM Eli Zaretskii <eliz@gnu.org> wrote:

> Emacs 29 has a fix for an old bug, whereby current-column etc. didn't
> take display strings and overlays into account; now they do.
>
> Of course, it could be that this fix introduced a bug in some
> not-so-simple situations, so I'd appreciate if you could show a simple
> recipe to reproduce the problem without the need of firing up
> company-mode and/or Eglot.
>

The only pathological problem -- that I know of -- is the "not-so-simple"
example/situation I described.  But it's pretty real and easy trigger
if you happen to use those two extensions which are both reasonably
popular.

If you are aware of the behaviour change , then I don't see the point
with coming up with a simpler repro: I'd just be showing what you
confirmed: that move-to-column now is affected by overlays such
as company's whereas before (emacs 27.2/28) it didn't.

If this is a bugfix in Emacs, then the logical conclusion is that the
problem should be fixed in company-mode.  It should somehow (tm)
find a way to create a visual popup that works in terminals for which
move-to-column behaves as before. Alternatively, some variation of
move-to-column that retains the old behaviour could be invented to
give the old behaviour.

Both these solutions would be better than the current defensive
one in Eglot, which makes Eglot LSP-abiding column-finding
less performant than it used to be.

João

[-- Attachment #2: Type: text/html, Size: 2053 bytes --]

  reply	other threads:[~2022-03-21 16:37 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 [this message]
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
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='CALDnm53Wb9v1qRSB2RX_uKqB6=hrNi2+8aOnCyNRfHJ1BnX7sg@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).