copy-file to remote works only with threads

[jeswcollins]

I'm writing about an issue with async.el we found when investigating an issue with ssh-deploy

(async-start (lambda() (copy-file path-local path-remote t t t t)) (lambda(response) (message "Copied with response: %s" response))

Fails to copy to a remote host (emacs 26, ssh).

Though the copy succeeds with threads (albeit with some timer error messages): (make-thread (lambda() (message "Copied with response: %s" (copy-file path-local path-remote t t t t))

[thierryvolpiatto]

Jesse W. Collins [email protected] writes:

I'm writing about an issue with async.el we found when investigating an issue with ssh-deploy

(async-start (lambda() (copy-file path-local path-remote t t t t)) (lambda(response) (message "Copied with response: %s" response))

Fails to copy to a remote host (emacs 26, ssh).

Be sure you have an authentification system (auth-source) that requires no user interaction i.e. enter password.

Though the copy succeeds with threads (albeit with some timer error messages): (make-thread (lambda() (message "Copied with response: %s" (copy-file path-local path-remote t t t t))

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.*

-- Thierry

Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997

[jeswcollins]

Yes, correct. EDIT: Oh I see the README now. I will add the recommended line to the init file.

[jeswcollins]

I don't see why I should need an auth-source, I have a key pair for ssh without user and pass. I also don't have use-package at the moment.