[Feature Request] File conflicts should not block a copying operation
First of all, thank you everyone for providing this great tool. I much appreciate it.
When I copy a large number of files, there will usually be some file conflicts (illegal filename, existing files, etc). A dialog pops up and asks me how to handle the file conflict. But this also stops the copying process. Why? Why not continue copying/moving all other non-conflicting files while waiting for user input?
I have had this issue for literally over 20 years, i asked myself this question back in Windows 98, and I just asked myself this question today. If I have a large file copy operation which takes like 3hrs, i will go away to do something else for 2hrs, only to come back to see the whole thing being stuck at 2% because my computer waited 1hr and 56mins for me to handle one single file conflict.
I don't know how to write a file manager (thanks again, everyone!), but i know programming languages well enough to know that you can create a buffer or a logfile or a stack or something like that, which stores all occurring file conflicts, and when the user gets to dealing with the error dialogs, this buffer/log/stack is progressively cleared.
Please, please, please make this a reality. Unattended file operations would be such an improvement in my (and i am sure many others) lives.