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

2019-11-17 Thread 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

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

2019-11-15 Thread Antoine Beaupré
On 2019-11-14 03:16:51, Daniel Kahn Gillmor wrote: > On Wed 2019-11-13 10:19:05 -0500, Antoine Beaupré wrote: >> Fundamentally, I think message-mode should treat emails the same way >> epg.el treats encrypted files: the data in the buffer isn't the same as >> the on-disk data, and there should be

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

2019-11-14 Thread Daniel Kahn Gillmor
On Wed 2019-11-13 10:19:05 -0500, Antoine Beaupré wrote: > Fundamentally, I think message-mode should treat emails the same way > epg.el treats encrypted files: the data in the buffer isn't the same as > the on-disk data, and there should be translation between the two. At > the very least, the

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

2019-11-13 Thread Antoine Beaupré
On 2019-11-12 18:03:58, Daniel Kahn Gillmor wrote: > Hi Antoine-- > > [epic story and funny rnat trimmed down to the salient bug reports and > feature requests because i'm a boring person] Hi! [I don't remember what RNAT (reverse network address translation) have to do with anything, but it's