Version: (using KDE 4.2.0) Installed from: Unlisted Binary Package The "autoskip" option in file copy / move operations is very helpful, however, it would be better if it would log the failed operations. Thus, the user could review the log and manually take care of failed operations.
Dotan, thanks -- I would extend this wish to log anything, and providing GUI way to check the logs. User could then filter out all unwanted data and focus only on errors for example. And just for the record -- this wish is recurring, very similar was posted for k3b, so maybe it would be good to have one common log mechanism?
I don't think that logging of _successfull_ operations is a good idea. It will add unneeded slowdown. KDE4 is quite slow even without such logging.
(I do many successfull operations regularly. I don't understand why all them should be logged and slowed.) At least, logging of _successfull_ operations shouldn't be a default behaviour, imho.
(On the other hand, I like the original Dotan Cohen's idea of logging failed/skipped operations.)
Logging should be able to log anything in general, defaults and when and where the log is used is another issue -- valid of course. For example logging successful burns in K3b seems very reasonable. My point is, this feature is rather for kdelibs (?) not only for copying, so every app could benefit from it.
*** Bug 158874 has been marked as a duplicate of this bug. ***
*** Bug 139528 has been marked as a duplicate of this bug. ***