bug#81538: 32.0.50; Eglot: Non-local exit during window/showDocument handling

Hi Troy,

On Sun, Aug 9, 2026 at 6:19 PM Troy Brown <[email protected]> wrote:
> > The reason I know is that I tested myself:
> Yeah, I had noticed that `eglot-handle-request` runs in a temporary
> buffer, so the locally registered post command hook was not being
> executed.

Yes
> When the problem happens, I notice that font-lock-mode is not enabled
> in the buffer and the buffer is not actually displayed...it stays
> buried.

OK...

> Try this.  The bug branch has larger files where I originally ran
> across the problem.  I also noticed that waiting for the LSP
> initialization to complete seems to increase the odds of the command
> failing (hence the "sleep-for" below).  The following works for me
> most of the time.

I still can't reproduce it on these much larger files. I tried about 10 times.

What operating system are you on?   Maybe Eli can shed light on whether
there are typically different process input  buffer sizes or other
configurations
that contribute to these discrepancies?

> > +                  (run-at-time #'findit 0 nil))))
> I'll try the new patch out.  FYI, I had also noticed that the call to
> "run-at-time" has parameters in the wrong order.  It should be
> `(run-at-time 0 nil #'findit)`.

Yes, you're right, this has to be fixed.

Can you confirm the new patch based on post-command-hook works for you?

João