From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: sbaugh@janestreet.com, 76064@debbugs.gnu.org
Subject: bug#76064: 31.0.50; Display issue with flymake-show-diagnostics-at-end-of-line
Date: Wed, 05 Feb 2025 18:31:54 +0200 [thread overview]
Message-ID: <867c648i9x.fsf@gnu.org> (raw)
In-Reply-To: <2taknuragpovq2uixzyrpacww26itozivptjpyvnuex4olan2b@xp3mttidrwh2> (message from Ergus on Wed, 5 Feb 2025 16:45:07 +0100)
> Date: Wed, 5 Feb 2025 16:45:07 +0100
> From: Ergus <spacibba@aol.com>
> Cc: sbaugh@janestreet.com, 76064@debbugs.gnu.org
>
> I think that we are just missing some property in the overlay that
> basically means "this text doesn't exist at all".
>
> Is it really that hard?
I think you don't realize the root cause of these problems. The root
cause is cursor position, not anything else. The overlay itself is
not the problem, the problem is that it tells the display engine to
show the cursor on the first character of the overlay string, when
point is actually _on_the_next_line_. That's why cursor motion
misbehaves.
IOW, it isn't about the overlay string text, it's about where to show
the cursor.
prev parent reply other threads:[~2025-02-05 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ikpp5m4v.fsf.ref@aol.com>
2025-02-04 23:24 ` bug#76064: 31.0.50; Display issue with flymake-show-diagnostics-at-end-of-line Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-02-05 13:46 ` Eli Zaretskii
2025-02-05 15:45 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-02-05 16:31 ` Eli Zaretskii [this message]
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=867c648i9x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=76064@debbugs.gnu.org \
--cc=sbaugh@janestreet.com \
--cc=spacibba@aol.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).