From: Romain Ouabdelkader <romain.ouabdelkader@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73863@debbugs.gnu.org
Subject: bug#73863: 30.0.91; Unexpected cursor movement with flymake-show-diagnostics-at-end-of-line
Date: Fri, 18 Oct 2024 21:10:02 +0200 [thread overview]
Message-ID: <CAJ8YToaCc=aOmntaqQyzTXEK1s-gP7bmT9+w9Fa-dhdXUDDvoQ@mail.gmail.com> (raw)
In-Reply-To: <86plnxmfdt.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 879 bytes --]
I can reproduce the issue on a C source file with clangd:
emacs -Q
M-x eglot
(setq flymake-show-diagnostics-at-end-of-line t)
```
unknown_function
void func();
```
[image: Screenshot 2024-10-18 at 21.06.43.png]
I can also reproduce on a elisp file without using eglot or any additional
packages:
emacs -Q /tmp/test.el
M-x flymake-mode
(setq flymake-show-diagnostics-at-end-of-line t)
```
;;; test.el --- Test for flymake diagnostics -*- lexical-binding: t -*-
;;; Commentary:
;;; Test file
very_long_variable_name_to_make_flymake_diagnostics_on_multiple_line
;;; Code:
(provide 'test)
;;; test.el ends here
```
[image: Screenshot 2024-10-18 at 21.02.10.png]
Make sure that the diagnostic is displayed on multiple lines (resize your
window if necessary). Place your cursor on
`very_long_variable_name_to_make_flymake_diagnostics_on_multiple_line` and
then press down.
[-- Attachment #1.2: Type: text/html, Size: 1369 bytes --]
[-- Attachment #2: Screenshot 2024-10-18 at 21.02.10.png --]
[-- Type: image/png, Size: 124453 bytes --]
[-- Attachment #3: Screenshot 2024-10-18 at 21.06.43.png --]
[-- Type: image/png, Size: 35549 bytes --]
next prev parent reply other threads:[~2024-10-18 19:10 UTC|newest]
Thread overview: 7+ 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 [this message]
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='CAJ8YToaCc=aOmntaqQyzTXEK1s-gP7bmT9+w9Fa-dhdXUDDvoQ@mail.gmail.com' \
--to=romain.ouabdelkader@gmail.com \
--cc=73863@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).