From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 54488@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#54488: 29.0.50; move-to-column/overlay-related regression in latest master, perhaps 28?
Date: Wed, 23 Mar 2022 05:34:39 +0200 [thread overview]
Message-ID: <83o81xe3zk.fsf@gnu.org> (raw)
In-Reply-To: <a405379e-0d87-3caf-12e6-4773741c69b2@yandex.ru> (message from Dmitry Gutov on Wed, 23 Mar 2022 01:55:17 +0200)
> Date: Wed, 23 Mar 2022 01:55:17 +0200
> Cc: 54488@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> On 22.03.2022 23:05, João Távora wrote:
> > > Why do you have to use move-to-column instead of forward-char?
> > >
> > > I don't remember! Is it exactly equivalent if you're standing in
> > the beginning of the line?
> >
> > Yes, if you have only text in the buffer (no images etc.).
> >
> >
> > Hmmm, it's interesting. Maybe I should just switch to that. Seems to fix
> > it. Until someone adds images to the source code i suppose. What's your
> > "etc"?
>
> Tabs?
Tabs are a problem anyway, because the compiler cannot know how wide
the tab is in the Emacs buffer. So if move-to-column is used to get
to the place where the error is indicated, tabs should be a problem
that is already handled specially, I think. And if so, it could be
handled specially (in a different way) when forward-char is used
instead.
Or what am I missing?
next prev parent reply other threads:[~2022-03-23 3:34 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
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 [this message]
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=83o81xe3zk.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).