Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] XDG-like trash bin #37

Open
alexcoder04 opened this issue Jun 8, 2022 · 0 comments
Open

[Feature request] XDG-like trash bin #37

alexcoder04 opened this issue Jun 8, 2022 · 0 comments
Labels
enhancement New feature or request verified Indicates that this issue is verified, so further triage can happen
Milestone

Comments

@alexcoder04
Copy link
Contributor

alexcoder04 commented Jun 8, 2022

Description

LeoConsole now has a built-in trash command, which moves deleted files into a trash folder. However, this has some disadvantages: e. g. what if multiple files with the same name are deleted? Or if the user decides to restore the file? Or delete files from trash after certain amount of time?

That's why I would suggest a system similar to the XDG trash spec, or even the XDG trash standard itself (then the trash folder has to be $XDG_DATA_HOME/Trash) (https://specifications.freedesktop.org/trash-spec/trashspec-latest.html). In short, the trash folder structure then looks like this:

trash
 | - files
 |   | - deletedfolder
 |   |  | - ...
 |   | - animage.png
 |   | - animage_1.png
 | - info
 |   | - deletedfolder.trashinfo
 |   | - animage.png.trashinfo
 |   | - animage_1.png.trashinfo

The .trashinfo files look like this:

[Trash Info]
Path=/home/user/Pictures/2020/animage.png
DeletionDate=2022-06-04T14:31:28
@alexcoder04 alexcoder04 added enhancement New feature or request needs-verification Indicates that this issue needs to be verified before further triage will happen labels Jun 8, 2022
@leonarudo leonarudo added verified Indicates that this issue is verified, so further triage can happen and removed needs-verification Indicates that this issue needs to be verified before further triage will happen labels Jun 10, 2022
@leonarudo leonarudo added this to the v2.0-servicing milestone Jun 10, 2022
@leonarudo leonarudo self-assigned this Jun 10, 2022
@leonarudo leonarudo modified the milestones: v2.0-servicing, v2.1 Jun 12, 2022
@leonarudo leonarudo removed their assignment Aug 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request verified Indicates that this issue is verified, so further triage can happen
Projects
None yet
Development

No branches or pull requests

2 participants