At now the "Copy" dialog contains only one input line "Destination path". Will be good to add also advanced options to this dialog, such as overwrite rules, at least. Because now I need to start copying process immediately, and wait indefinite time, when the duplicated file/folder will be detected and overwrite dialog appeared, this is very annoying. Also will be good to see most of other options, that can be forced before starting the copy process, to not break it later with user interruption by questions/confirmations.
After the copy has started, the "File Already Exists" window pops up asking for action, you can overwrite file(s), overwrite only the older files and choose to apply the same to all next files. Does it solve your needs? That window is handled by KIO, not Krusader, but the options could be given as parameters, meaning you can set it before the start of operation.
> After the copy has started, the "File Already Exists" window pops up asking for action The problem is that this "After the copy has started" is not asks immediately, you must wait indefinite time after start copy action on Krusader when the first file duplicate will be detected. So much conveniently to set this argument before starting process, to pass to. Kio parameter to force overwrite all.
Please, add Overwrite all older or Update option, like in Konsole cp -u, --update copy only when the SOURCE file is newer than the destination file or when the destination file is missing.
You're right, you can set a global action but have to wait until it pops out. Some option could be added to the copy/move window (there several wishes about it), also given that KIO has much improved its usage/options. Moving to wishlist.
This could be potentially turned into a more generic problem of operations stalling waiting for user interaction. My occasional issue is similar, but I tend to encounter it with the Synchronize Folders function as it whines about not being able to access files rsync had no problem making. It's not just quite tiresome to keep on dismissing the error popup that can be only dismissed anyway, but the process also tends to be quite slow with a lot of small files due to the likely sequential processing with synchronous I/O, so it's not uncommon that the host is left on its own while it's working, but it gets stuck on such a prompt. I used to use Total Commander which had a kind of a fix for at least the reported problem. Wasn't optimal, but the first time it wanted to overwrite a file, it had an option to automatically overwrite all the following files too, basically what's mentioned in Comment 1. It didn't have a solution for error popups though, likely the assumption was that they were rare, and it was also faster to enumerate smaller files despite the infamously slow Windows I/O, so it likely used a more efficient I/O strategy, therefore the error popups were less of a problem especially on HDDs. The lowest hanging fruits are the already mentioned ones, but this could be also solved by moving file entries into a user interactivity queue when they need attention while continuing to process other files, and as the user would process prompts, the entries would be either discarded or moved back depending on what the user desires.