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

[Barry Fishman <barry@ecubist.org>]

On 2023-10-05 19:24:51 +03, Eli Zaretskii wrote:
> 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.
...
> Displaying a buffer sometimes modifies the buffer (via font-lock).

Yes.

I was just looking for a simple common interface that would:

 * Encapsulated common code to reduce code duplication.  Avoid platform
   specific handling such as systems without threads.

* Handle simple cases simply.  It may be that the locking buffers is not
  generally helpful.  It probably isn't, but if it were, programmers
  could pass an empty list of buffers, or release the buffers when they
  were ready to update them.

* Provide a common function (grep-able) so that the implementation
   could change with time.

I was just suggesting that rather that waiting for some global solution
to be found, a less complex approach be considered in the mean time.
Where "pain points" could be considered a case by case basis, but still
provide a common mechanism to use.

-- 
Barry Fishman


---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)