From: Eli Zaretskii <eliz@gnu.org>
To: Romain Ouabdelkader <romain.ouabdelkader@gmail.com>
Cc: sbaugh@janestreet.com, 73863@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#73863: 30.0.91; Unexpected cursor movement with flymake-show-diagnostics-at-end-of-line
Date: Sun, 20 Oct 2024 18:49:27 +0300 [thread overview]
Message-ID: <86froqixko.fsf@gnu.org> (raw)
In-Reply-To: <CAJ8YToY2YBSsMzc6oc3fCcwUNNHCDT3CY7ifHfFFPF2yhSBJJg@mail.gmail.com> (message from Romain Ouabdelkader on Sun, 20 Oct 2024 17:01:44 +0200)
> From: Romain Ouabdelkader <romain.ouabdelkader@gmail.com>
> Date: Sun, 20 Oct 2024 17:01:44 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, sbaugh@janestreet.com, 73863@debbugs.gnu.org
>
> Sorry, I realized I wasn't clear about the behavior I was expecting.
>
> I would expect the cursor behavior to remain consistent whether diagnostics are present or not, especially
> since diagnostics can appear and disappear during editing.
That's not possible, because the diagnostic is displayed using an
overlay string, and Emacs cannot show a cursor inside such a string
unless a Lisp program tells it exactly where to put the cursor. IOW,
for the cursor-positioning purposes, overlay strings are considered as
indivisible chunks of display.
> For example:
> Screenshot 2024-10-20 at 16.56.48.png
> Here, when press C-n once, I expect the cursor to go here:
> Screenshot 2024-10-20 at 16.57.59.png
Under the default value of line-move-visual, this is not possible:
Emacs is required to show the cursor inside the next _screen_ line,
not the next _logical_ line. Compare that with the situation where
the diagnostic string is part of buffer text -- in that case you'd
want the cursor to end up inside the next screen line, which is
wrapped from the long line starting with "unknown_function".
> I.e. the behavior would be the same as if there were no diagnostics in the buffer.
> I'm not sure if that's actually feasible or if there is an issue with this behavior.
It isn't feasible.
> I tried your patch but it makes the cursor go on the diagnostic which i find surprising, I believe the cursor
> should not be able to move into a diagnostic:
> Screenshot 2024-10-20 at 17.00.18.png
We could have the cursor after the diagnostic, if we don't put the
'cursor' property at all.
So these are the possible solutions for this situation:
. don't change anything and live with the minor irregularity in the
cursor positioning in what I consider to be rare cases
- variation: turn on truncate-lines in such cases
. don't put the 'cursor' property on the diagnostic, in which case
C-n will place the cursor after the end of the diagnostic on the
screen line where the diagnostic ends
. put the 'cursor' property at the last character of the diagnostic
string, and have it displayed there
. calculate the character on which to put the 'cursor' property
dynamically using some convoluted logic
. implement display of diagnostics in a tooltip instead
Any other suggestions?
next prev parent reply other threads:[~2024-10-20 15:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:09 bug#73863: 30.0.91; Unexpected cursor movement with flymake-show-diagnostics-at-end-of-line Romain Ouabdelkader
2024-10-18 16:08 ` Eli Zaretskii
2024-10-18 16:24 ` Romain Ouabdelkader
2024-10-18 18:31 ` Eli Zaretskii
2024-10-18 19:10 ` Romain Ouabdelkader
2024-10-19 13:15 ` Eli Zaretskii
2024-10-19 13:41 ` Romain Ouabdelkader
2024-10-20 7:25 ` Eli Zaretskii
2024-10-20 9:28 ` João Távora
2024-10-20 11:22 ` Eli Zaretskii
2024-10-20 11:38 ` João Távora
2024-10-20 11:49 ` Eli Zaretskii
2024-10-20 14:42 ` João Távora
2024-10-20 15:01 ` Romain Ouabdelkader
2024-10-20 15:49 ` Eli Zaretskii [this message]
2024-10-20 16:23 ` Eli Zaretskii
2024-10-20 15:31 ` Eli Zaretskii
2024-10-20 15:39 ` João Távora
2024-10-20 16:30 ` Eli Zaretskii
2024-10-20 16:58 ` João Távora
2024-10-20 17:50 ` Eli Zaretskii
2024-10-20 18:05 ` João Távora
2024-10-20 18:28 ` Eli Zaretskii
2024-10-20 19:18 ` João Távora
2024-10-18 19:16 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18 19:25 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86froqixko.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73863@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=romain.ouabdelkader@gmail.com \
--cc=sbaugh@janestreet.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).