When you empty the trash you are told you cannot undo this, but the undo option is still available in the menu; it leads to an error about not being able to rename files. Reproducible: Always Steps to Reproduce: See video
The Undo action refers to the previous operation, e.g. if you copy a file from A to B, then empty the Trash, then you can still Undo the copy.
Thank you for the explaination. It would be more clear if the error message told you that you could not rename because the file no longer exists. That would clear up things considerably.
this problem with all operating systems or particular one
one way is to rename the file is that first restore this than change the name.
The bug here is that whatever made the file no longer exist isn't being added to the undo/redo stack. It works properly when the file has been put into the trash, but not when the file has been deleted. I was able to reproduce that in Dolphin and KIO from git master (i.e. KF 5.46 and Dolphin 18.08). That seems like a Dolphin-specific issue though, not KIO's problem. Moving there.
I don't understand, are you saying that a delete job should be added to the undo stack? That's just not possible. (What we could do is to add a "cannot be undone" warning in the delete dialog)
(In reply to Elvis Angelaccio from comment #6) > I don't understand, are you saying that a delete job should be added to the > undo stack? That's just not possible. > > (What we could do is to add a "cannot be undone" warning in the delete > dialog) That would be nice, for sure. But what's the technical barrier to being able to undo a delete job? Seems like we could cache the to-de-deleted file in memory or somewhere on disk or for a short period of time just prior to deletion, to allow the job to be undone. But if that's too hairy technically, a warning would be nice too.
(In reply to Nate Graham from comment #7) > (In reply to Elvis Angelaccio from comment #6) > > I don't understand, are you saying that a delete job should be added to the > > undo stack? That's just not possible. > > > > (What we could do is to add a "cannot be undone" warning in the delete > > dialog) > > That would be nice, for sure. But what's the technical barrier to being able > to undo a delete job? Seems like we could cache the to-de-deleted file in > memory or somewhere on disk or for a short period of time just prior to > deletion, to allow the job to be undone. Why? Why not just use the Trash? This is exactly what is made for. Shift+Del means _permanent_ deletion everywhere. If that's not clear enough, we should really explain it better in the delete dialog.
(In reply to Elvis Angelaccio from comment #8) > Shift+Del means _permanent_ deletion everywhere. If that's not clear enough, > we should really explain it better in the delete dialog. Sounds good. Here, have a patch! https://phabricator.kde.org/D12420