Async Operations in TRAMP

Async Operations in TRAMP

[Nordlöw]

Is it possible to make the dired/tramp file operations, typically
remove, copy and move, asynchronous by spawning them as separate
processes? This would make Emacs TRAMP even more unique and amazing...

/Nordlöw

Re: Async Operations in TRAMP

[Michael Albinus]

Nordlöw <per.nordlow@gmail.com> writes:

> Is it possible to make the dired/tramp file operations, typically
> remove, copy and move, asynchronous by spawning them as separate
> processes? This would make Emacs TRAMP even more unique and amazing...

Anything goes, of course ...

However, Tramp's main purpose is to provide handlers for magic file name
operations. So it might be useful to introduce a general asynchronous
mode in dired first, and to add Tramp handlers later on.

There are also some problems to be solved, for example if you want to
access a file, which is being copied or removed. And how to indicate,
that an operation has been finished, and it is safe to access the
resulting file.

I vaguely remember there has been a discussion about, but I have no
pointer.

> /Nordlöw

Best regards, Michael.

Re: Async Operations in TRAMP

[José A. Romero L.]

On 19 Lut, 11:26, Nordlöw <per.nord...@gmail.com> wrote:
> Is it possible to make the dired/tramp file operations, typically
> remove, copy and move, asynchronous by spawning them as separate
> processes? This would make Emacs TRAMP even more unique and amazing...
>
> /Nordlöw

It  is certainly possible to launch a separate elisp interpreter from
emacs, and delegate to it commands for asynchronous execution. For an
example have a look here:

    http://www.emacswiki.org/emacs/Sunrise_Commander#toc4

that  one  implements only the copy and move operations, but it would
be trivial to add remove too, or any other command that can be put in
the background.

Cheers,
--
José A. Romero L.
escherdragon at gmail.com
"We who cut mere stones must always be envisioning cathedrals."
(Quarry worker's creed)