-
-
Notifications
You must be signed in to change notification settings - Fork 844
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
^C does not work as expected when using lrzsz #282
Comments
You may need to press |
rttyd uses a custom protocol without crc check which isn't reliable, you may get corrupted data. |
I don't want to invent a new protocol for file transferring. someone may ssh to another host in a ttyd terminal, if ttyd uses a custom protocol, the user will need to install ttyd on the host to send/recv files. zmodem is a standard protocol, which means it's package exists in most popular systems, and is easier to install. I agree that the user experience of zmodem on ttyd is not good for now, but I prefer to use it, and will keep improving it. |
On the wire, Ctrl-C is not the method to cancel a Zmodem transfer, it is per the spec (see page 6) five ASCII CAN's (Ctrl-X). Reading the issue, it sounds like Ctrl-C will cancel the zmodem.js UI part of the transfer, leaving the remote side still trying to send. Press Ctrl-X 5 or more times and that should terminate the remote (l)rzsz.
Zmodem does have one drawback on today's systems: it cannot prevent either side from emitting the ssh termination sequence (~.). It's not too likely to happen in the wild, but I usually ensure I do 'ssh -e none' when I know I might be using Zmodem in a session. (Kermit can be made ssh-safe, and also terminates with three Ctrl-C's.) |
Describe the bug
rz
and press Ctrl + C. The popup does not disappear.rz
to receive the selected file and press Ctrl + C. A lot of junk characters appear in the terminal.sz
to send a file and press Ctrl + C. The terminal is locked.Environment:
Additional context
Related to #99
I thought
lrzsz
used Ctrl + X to cancel the action.The text was updated successfully, but these errors were encountered: