Cannot abort copy operation in process with Ctrl-C

[Lewis Rosenthal]

COPY should be interruptible (with a prompt, at best, and with a warning that the operation was interrupted before completion, at a minimum).

Presently, copying a large set of large files is terribly inconvenient, as a false start requires a SigKill? to stop the copy in progress.

Honestly, I have no idea whether this is consistent with CMD's COPY or not, but with file sizes what they are today, this is an annoyance, at best, and the purpose of this ticket is not compatibility or parity with CMD, but better behavior.

[andi.b]

You mean copy of a single large file should be interruptible I guess. As copying a lot of files (copy /u/s ....) is interruptible anyway. Maybe/probably CTRL-C is only checked before/after each file. Correct?

[Steven Levine]

That's not quite how it works. Ctrl-C generates a signal and 4OS2 makes use of setjmp/longjmp and and exception handler, so it does not need to be checked, per se. The original 4OS2 authors chose to do the copy in a must complete section which has the effect of disabling signals for the duration of the copy.

I'm not quite sure why the authors did not wrap the DosCopy? in a setjmp() as they did for the copy a few lines further down.

FWIW, cmd.exe allows the copy to be interrupted.

[Steven Levine]

Ticket retargeted after milestone closed