Subject: bug#77942: 31.0.50; replace-region-contents gets stuck

From: Stefan Monnier <[email-masked]>
Date: Tue, 22 Apr 2025 10:33:09 -0400

>> MAX-SECS isn't working as expected said Stef elsewhere.
> If you set it to zero, it must work as expected.  If it doesn't, it's
> a bug.

He does want to trigger the diff code, tho.  The problem is that in his
test case, the diff code consults checks for a timeout too infrequently
(e.g. not at all for a whole hour).

        Stefan