unifying and automating draft ("postpone/resume") behavior [was: Re: notmuch "lost" email during power failure]

[Daniel Kahn Gillmor]

On Fri 2019-11-15 10:08:02 -0500, Antoine Beaupré wrote:
> The individual calls are not what's prohibitively expensive. The problem
> is latency. Even if it just takes 100ms[1] to save the file to the disk,
> that's a huge delay in terms of human interface, because the entire
> Emacs UI will *freeze* for that amount of time whenever it thinks it
> should do an autosave.

Surely the problem there is that the Emacs UI is freezing and blocking
to do something that has nothing to do with interactive work!

Is it not possible in 2019 to have emacs handle its autosave
functionality in either a background thread, or in a non-blocking
asynchronous interaction with a co-process?

             --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20191116/ff83b87f/attachment.sig>