-
Notifications
You must be signed in to change notification settings - Fork 16
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
report/display rsync output in separate buffer? #12
Comments
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 to do when you have 2 or more rsyncs running? |
How about not kill the process buffer and let it auto pop out when the the process finished with an error? |
Looks like the error variable err in dired-rsync--filter is not defined. |
The hook is called in the context of the failed process buffer.
@QiangF err can be nil. What error are you seeing? |
I see. I am just afraid of possible unnoticed failures. |
There seems no visual feedback when running dired-rsync. Am I wrong? |
See |
It would be nice to have a buffer which collects rsync output, particularly for lengthier rsync operations (but also to check errors etc.)
The text was updated successfully, but these errors were encountered: