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 19:05:53 +0200 [thread overview]
Message-ID: <83fsnbfd72.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm53Wb9v1qRSB2RX_uKqB6=hrNi2+8aOnCyNRfHJ1BnX7sg@mail.gmail.com> (message from João Távora on Mon, 21 Mar 2022 16:37:18 +0000)
> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 21 Mar 2022 16:37:18 +0000
> Cc: 54488@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
>
> 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.
The questions is: does current-column, move-to-column, etc. on master
indeed report the column number and move to the place whose column
number _on_display_ is as you ask them? If they do, then this is the
correct behavior, and features that expect something else should
adapt. But if move-to-column moves to a column that is visually
incorrect, I'd still like a simple reproducer. Even if one must use
company-mode and eglot, can you post a recipe that doesn't involve
their installation via package.el? Suppose I download the relevant
*.el files to my system and manually load them as needed, can you show
a recipe that loads whatever is needed and then reproduces the issue?
next prev parent reply other threads:[~2022-03-21 17:05 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fsnbfd72.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.