[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2022-12-05 Thread dft
https://bugs.kde.org/show_bug.cgi?id=412163 --- Comment #12 from dft --- I would like to bring this up again and keep it simple with another use case. You have a folder of 500GB and want to copy to a drive that has 480GB free. Destination is ZFS or BTRFS with compression means it should EASILY

[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2021-11-10 Thread dft
https://bugs.kde.org/show_bug.cgi?id=412163 --- Comment #11 from dft --- Please can we just disable checking for freespace. It's now end 2021 and Dolphin is useless for merging. It means I have to use rscync or krusader to do such a simple task... Again I have to copy 420GiB folder from Drive A

[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2021-06-14 Thread dft
https://bugs.kde.org/show_bug.cgi?id=412163 --- Comment #10 from dft --- I think you are over complicating the solution. It it does not need to know it was cancelled. Say you are copying a folder of movies. You cancel cause you have to go out or what ever and shutdown. Now you come back and

[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2021-06-14 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=412163 --- Comment #9 from Ahmad Samir --- The code doesn't know that some files were copied, and then the copy was cancelled then resumed :) The only way to know would be to list all the dirs in both source and destination, which would take time depending

[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2021-06-14 Thread dft
https://bugs.kde.org/show_bug.cgi?id=412163 --- Comment #8 from dft --- I don't think you need to compare, Dolphin just needs a SKIP ALL that DOES NOT look and assume there isn't enough free space. EG You copy 16GB, you cancel at 14GB for what ever reason. Free space (after the 14GB) is 10GB.

[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2021-06-14 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=412163 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #7 from Ahmad

[frameworks-kio] [Bug 412163] Only check for required free space after asking the user whether or not to merge, and if merging, intelligently determine the space needed based on what needs to be merge

2019-10-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=412163 Nate Graham changed: What|Removed |Added CC||kdelibs-b...@kde.org Ever confirmed|0