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

2023-10-05 Thread Barry Fishman
On 2023-10-04 19:21:36 +02, Emanuel Berg wrote: > joakim wrote: > >> - You have a single Emacs instance, you do everything in it, >> but you get sad when a long running operation, in this >> case Gnus, or generating your Org agenda, takes a long >> time, and you have to wait. >> >> - You sta

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

2023-10-05 Thread Eli Zaretskii
> From: Barry Fishman > 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 origina

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

2023-10-05 Thread Barry Fishman
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

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

2023-10-05 Thread Eli Zaretskii
> From: Barry Fishman > Date: Thu, 05 Oct 2023 17:34:01 -0400 > > 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 co