Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't copy large file from some remote machines. #111

Closed
failable opened this issue Apr 19, 2019 · 10 comments
Closed

Can't copy large file from some remote machines. #111

failable opened this issue Apr 19, 2019 · 10 comments

Comments

@failable
Copy link

failable commented Apr 19, 2019

When trying to copy a large remote file to my local directory, dired-async-do-copy creates a new buffer call *emacs* with content Lisp expression: File log.txt is large (336.9M), really copy? (y or n) . I'm not able to answer y in this buffer and a character y is inserted in to this buffer. The process of this buffer is waiting for reply until I kill it.

But this did not happen to every remote machine I tested with the same large file size. Some will never prompt for confirmation and copy started automatically. I've tried to set dired-no-confirm, but no magic happened.

Small files are always ok.

Local emacs version: GNU Emacs 26.2 (build 1, x86_64-apple-darwin18.5.0, Carbon Version 158 AppKit 1671.4) of 2019-04-15

Thanks.

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Apr 19, 2019 via email

@failable
Copy link
Author

May I ask what do you mean by 'method'? I setup dired-async, use tramp to open a remote dired buffer and press C on the specific file to copy.

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Apr 20, 2019 via email

@failable
Copy link
Author

ssh.

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Apr 21, 2019 via email

@failable
Copy link
Author

Thanks.

@darkfeline
Copy link
Contributor

I started experiencing this, why does this happen?

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Jun 6, 2022 via email

@darkfeline
Copy link
Contributor

Why do you say it's a tramp bug? If we know it's a tramp bug, is there an upstream report?

I am just trying to understand it since it feels mysterious to me.

The bug you linked in #111 (comment) says that scp doesn't work, use ssh instead, and now you say ssh doesn't work, use scp instead?

@thierryvolpiatto
Copy link
Collaborator

thierryvolpiatto commented Jun 10, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants