From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 54488@debbugs.gnu.org, 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 14:32:15 +0200 [thread overview]
Message-ID: <831qyvfpv4.fsf@gnu.org> (raw)
In-Reply-To: <87bkxzdccp.fsf@gmail.com> (message from João Távora on Mon, 21 Mar 2022 06:54:46 +0000)
> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 21 Mar 2022 06:54:46 +0000
> Cc: dgutov@yandex.ru
>
> In short, it seems that in the presence of the overlays created by
> company-mode and in presence of a narrowing, the move-to-column function
> does not function the way it used to.
Yes.
> Eglot uses 'move-to-column' to go that precise place and highlight the
> warning.
>
> In Emacs 27.2, move-to-column is unaffected by previous company-mode
> overlays, even if the current line is being co-used visually by the
> overlay. It moves to the right buffer position.
>
> In Emacs master, this isn't true. It seems to be confounded by the
> company-mode overlay and moves to eob, _beyond the narrowing_, which
> eventually breaks Eglot with a backtrace such as this one:
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.
next prev parent reply other threads:[~2022-03-21 12:32 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 [this message]
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
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=831qyvfpv4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54488@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.com \
/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).