bug#81514: 32.0.50; Eglot messages progress reporter shows errors

João Távora

On Wed, Aug 5, 2026, 12:34 Sean Whitton <[email protected]> wrote:

> João Távora [05/Aug 12:19pm +01] wrote:
> > On Wed, Aug 5, 2026, 12:15 João Távora <[email protected]> wrote:
> >
> >> Afaik, while Eglot had its shortcomings in its usage of progress
> >> reporters, now hopefully fixed, the real trigger for this regression
> was a
> >> backward incompatible change in progress reporters. Presumably Stéphane
> 's
> >> patch addresses that. If you don't install it, it could be that other
> Elisp
> >> code out there making similar poor usage of reporters as Eglot did until
> >> now will start breaking.
> >>
> >
> > [ Sorry sent too early.]
> >
> > ...anyway, could be a risk worth taking for the general improvement of
> > things, or not. Maintenance policy call... In any case, if so, it should
> be
> > listed under backward incompatible Lisp changes.
>
> Thanks, though I don't think I yet see what's backwards incompatible
> about it.  I'd like to know exactly what this is trying to fix and how.
>

The Lisp backward incompatibility (a stricter erroring behaviour if I'm not
mistaken) was already installed! The bisection in the beginning of this bug
report points to it directly. How do you think Eglot started breaking?

The patch by Stéphane may or may not mitigate it completely. I meant
earlier that you _may_ decide to keep the backward incompatibility if you
think it's worthwhile, but in that case document it ("blabla now errors if
you do this and that, whereas in the past it didn't...")

João

>