Subject: bug#70541: track-changes-mode logs warnings (with input method, in Eglot buffer)

From: Eli Zaretskii <[email-masked]>
Date: Mon, 29 Apr 2024 11:45:18 +0300

> From: Ihor Radchenko <[email-masked]>
> Cc: Eli Zaretskii <[email-masked]>, [email-masked], [email-masked],
>  Stefan Monnier <[email-masked]>
> Date: Mon, 29 Apr 2024 08:36:37 +0000
> 
> João Távora <[email-masked]> writes:
> 
> > On Mon, Apr 29, 2024 at 7:09 AM Eli Zaretskii <[email-masked]> wrote:
> >>
> >> initial too-naïve attempts caused elsewhere.
> >>
> >> So I'd very much prefer that Quail signaled to applications that it's
> >> in the middle of handling some complex input, and that applications
> >> which track changes ignored the changes made during this period.
> 
> Would adding `combine-change-calls' to Quail be an option?

I don't think so, since more than a single function is involved
(AFAIU).

> AFAIU, calling the change hooks in the middle of quail input is the main
> culprit of the problems we are discussing here.

The original Quail code inhibits the modification hooks, so this
cannot be the culprit, can it?