Bug 496993 - Replacing a file with another file with the same name should cause the replaced file to be trashed (instead of permanently deleted).
Summary: Replacing a file with another file with the same name should cause the replac...
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.08.3
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-03 16:54 UTC by Fernando M. Muniz
Modified: 2024-12-05 15:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando M. Muniz 2024-12-03 16:54:43 UTC 
Currently when a file is replaced by another with the same name, the replaced file is permanently deleted.

I'm requesting the default to be trashing the replaced file, to make the replaced file easily recoverable in case of accidents.
Comment 1 Fernando M. Muniz 2024-12-03 17:54:37 UTC 
It's impossible to recover trashed files into the same place as the files with the same name are locate. So this won't be an issue.
Comment 2 Fernando M. Muniz 2024-12-03 18:46:53 UTC 
(In reply to Fernando M. Muniz from comment #1)
> It's impossible to recover trashed files into the same place as the files
> with the same name are locate. So this won't be an issue.

Actually you can easily bypass the fix by simply dragging the trashed file...

So maybe when this situation happens use the /tmp folder for a brief moment? As in, create a folder in it with a randomized name to switch the files around.
Comment 3 TraceyC 2024-12-05 15:35:20 UTC 
This seems reasonable