From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
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 21:28:22 +0300 [thread overview]
Message-ID: <864j56iq7t.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm53Ljfr33znhMeMQaPXH78JiQZYS36nfuoY=CN6Y_bbXBA@mail.gmail.com> (message from João Távora on Sun, 20 Oct 2024 19:05:56 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Sun, 20 Oct 2024 19:05:56 +0100
> Cc: sbaugh@janestreet.com, romain.ouabdelkader@gmail.com,
> 73863@debbugs.gnu.org
>
> On Sun, Oct 20, 2024 at 6:51 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Something like that, yes.
>
> Sounds absolutely hellish to implement.
I wouldn't be so sure. The infrastructure for, for example, removing
portions of buffer text when saving to a file already exists, and we
use it in some modes.
> Even the most basic isearch need to be aware of that somehow.
I'm not sure. Why shouldn't Isearch find matches in the diagnostics?
Searching an Office document does find matches in comments, for
example.
> Anything that works with buffer text in Emacs would have to somehow
> cause that undo/redo.
Not anything, IMO.
Anyway, I'm not going to work on this, so it's an idea, no more, no
less. My point is that all the tricky display issues are completely
gone once we use buffer text. So an additional effort in Lisp
programming could be justified.
next prev parent reply other threads:[~2024-10-20 18:28 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
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 [this message]
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=864j56iq7t.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).