Alex Bennée

I don't see any reason why we couldn't improve the local to local case although I'm not so sure about how a UI for previewing would work. I guess it...

This looks like a good clean-up but I'm seeing breakage on remote-to-remote copies: Debugger entered--Lisp error: (wrong-type-argument sequencep 47) mapconcat(identity "/home/alex/mysrc/dired-rsync.git/LICENSE" " ") s-join(" " "/home/alex/mysrc/dired-rsync.git/LICENSE") (format "'%s %s -e...

Yes currently dired-rsync blindly tries to set up a portfwd to backchannel the rsync. However we should be able to special case the same remote to same remote case.

Yes - we need to expand the handling of the file parts. A quick workaround would be to set up an alias in .ssh/config and then drop the port number...

You can actually get to the buffer by doing a M-x list-processes and clicking/selecting the process buffer. I could probably add a key shortcut to dired for it but what...

@QiangF err can be nil. What error are you seeing?

Would it be all dired marks or all dired marks bellow the invoked directory. In principle you could write a fetcher to collect all the paths.

For point 2 we already have a hook into the sentinel for detecting the passphrase appearing. Maybe we should have a cleaner hook for this?

It's hard to gauge that from the rsync output. If there is an invocation that gives a clean list of failed files we could scrape that information from the process...

You could probably hack something up by let binding `dired-rsync-source-files` to provide your list of files and then calling `dired-rsync`. Something like (untested): (defun my-dired-rsync-workflow() (interactive) (let ((dired-rsync-source-files (lambda() "tramp-path-from-source")))...