| Summary: | Suggestion - Conflict Resolution All at Once | ||
|---|---|---|---|
| Product: | [Applications] krusader | Reporter: | Jim <jwagner> |
| Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | krusader-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
SUMMARY I regularly move and copy a large number of files / directories, both at work & home. When I do so, the conflicts pop up one at a time, asking me if I want to write into it if it's a directory, overwrite it if it's a file, skip it, rename it, or cancel the whole process. This sometimes takes a VERY long time when migrating a large tree, so I cannot just start it and leave to do something else because the process will stall until the user input box is taken care of. It would be nice if there were an option for Krusader to locate all conflicts when a copy/move first begins and pop up a scrollable box that would allow the user to resolve all of these at the start. STEPS TO REPRODUCE 1. Create a large directory tree with files in. 2. Copy it to an external drive. 3. Update the original. 4. Copy the tree to the external drive. Method A 5. Watch as the conflicts trickle in slowly, or leave to fix something else and come back to a box sitting there for who-knows-how-long asking if you want to overwrite a 0 byte flag file or something else trivial. 6. Realize that you now have to stay late because there's not enough time to complete the process before you're supposed to leave to go home. Method B 5. Start a copy and go to bed so you can use your laptop the next day. 6. See it only being a quarter done when you get up because Krusader is asking if I want to write into a directory with the same name and has been doing nothing all night long. Method C 5. Start a copy process and begin working on something else on the same computer. Get into it to where you're not paying complete attention to your screen. 6. When the conflict resolution box pops up and you don't immediately notice, type the code you want to be in the program you're writing because the focus has been stolen by Krusader, then go back and try to find what files were affected & what their original names were. All Methods: 7. Gnash your teeth in frustration. ----- Yes, I could use rsync to copy the files / directories, but I would like to have some idea of the progress being made, estimate of how long it's going to take yet, and rsync will kabosh a file with the same name on the target rather than letting me know that there's a conflict and let me decide what to do about it. (Sometimes the file on the PC isn't as good as the one on the backup drive.)