Re: A simple(perhaps dumb) idea for a more responsive emacs

[Eli Zaretskii]

> From: Barry Fishman <barry@ecubist.org>
> Date: Thu, 05 Oct 2023 08:49:20 -0400
> 
> Otherwise it would put the buffers in read-only mode, and spawn a thread
> to do the slow operation and return.  When that thread completed, an
> event would start second thunk which would update the buffers, and then
> the original mode of the buffers would be restored.

Making buffers unwritable while the slow operation runs is probably
problematic, as it doesn't allow the user to keep working on the
buffer while the operation runs.

> This would allow a slow operation not to hold up the user from doing
> anything except changing the effected buffers.  It would still let the
> buffer and screen update happen in the appropriate threads, which might
> be limited by the window system being used.

Displaying a buffer sometimes modifies the buffer (via font-lock).