From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@janestreet.com, 73863@debbugs.gnu.org,
romain.ouabdelkader@gmail.com
Subject: bug#73863: 30.0.91; Unexpected cursor movement with flymake-show-diagnostics-at-end-of-line
Date: Sun, 20 Oct 2024 12:38:33 +0100 [thread overview]
Message-ID: <CALDnm524+=cKz5J1VQ7Zv1MoNGjsaoBQQw6EUH+eAy0WO2gSrQ@mail.gmail.com> (raw)
In-Reply-To: <86zfmzhvdb.fsf@gnu.org>
On Sun, Oct 20, 2024 at 12:22 PM Eli Zaretskii <eliz@gnu.org> wrote:
> When the diagnostic overlay wraps to the next screen line, it is
> strange to see the cursor at the beginning of the diagnostic after
> C-n, since users generally expect C-n to move to the next screen line.
That may be so, and probably it is so. But I'd make sure to keep the
current behaviour (or at least unsurprising behaviour) when the
diagnostic(s) overlay (overlays?) _doesn't_ (don't?) wrap to the next
screen line.
João
next prev parent reply other threads:[~2024-10-20 11:38 UTC|newest]
Thread overview: 28+ 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 [this message]
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
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-27 10:56 ` Eli Zaretskii
2024-10-30 23:57 ` Romain Ouabdelkader
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALDnm524+=cKz5J1VQ7Zv1MoNGjsaoBQQw6EUH+eAy0WO2gSrQ@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=73863@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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.