trash-restore terminates too eagerly

[pkzc]

Is your feature request related to a problem? Please describe. When trash-restore is given a long list of item numbers to restore and encounters an already existing destination file, it reports an error and terminates. But once I gave that list, then I was serious about it. Now, my list of numbers is invalidated, and I have to start working from scratch again.

Describe the solution you'd like The error message is all right, but the restore operation should go on with the rest of the files in the trashcan.

Describe alternatives you've considered The logic of not overwriting an existing file without --overwrite is valid, but it is beyond me to grasp why exiting immediately upon the first occasion. The right thing in my opinion would be to restore the restorable and not restore the unrestorable, and writing a proper log in the process:

file1 restored file2 skipped (in case of no --overwrite option) file3 overwritten (in case of --overwrite)

It would also be beneficial if the file names in the report were full paths like reported by trash-list and not the basename as it is now in the error report of trash-restore, which is of little use.

Additional context None.