Re: Asynchronous insertion / saving of buffers

[Ted Zlatanov]

On Fri, 13 Apr 2012 14:44:31 +0200 Michael Albinus <address@hidden> wrote: 

MA> However, this is not sufficient. File name handlers, like Tramp, know
MA> only primitive operations. In the environment where these primitive
MA> operations are called, further actions will be applied, assuming that
MA> the primitive operation has finished once it returns. In case of
MA> `insert-file-contents', further operations will be applied, which fail
MA> in the asynchronous case due to the missing buffer contents. Examples:

MA> - Call of `after-find-file', which expands for example tar files

MA> - Operations from vc-*, which check a status (like reading and parsing
MA>   dirstate in vc-bzr)

MA> Obviously, we need some design how to handle asynchronous file
MA> operations. Any proposals?

Maybe you can approach this similarly to url-future.el?

I intended to make it generic but only had use for the URL retrieval
case; you'll see it's easy to adapt it to be generic.  Futures map well
to combinations of synchronous/asynchronous operations, in my
experience, and they can be chained.

Ted