After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619408 - Add a "Trash Autopurge" functionality
Add a "Trash Autopurge" functionality
Status: RESOLVED DUPLICATE of bug 149572
Product: nautilus
Classification: Core
Component: Trash
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-23 08:33 UTC by antistress
Modified: 2010-05-23 15:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description antistress 2010-05-23 08:33:43 UTC
Trash purge is typically a function that could be automated.

Most applications propose such a functionality (i.e. my webmail let me configure it to automatically delete messages in the trash after 7 days)

At present time lots of people get bored with emptying the trash so they prefer definitely delete files (shift+suppress)
But sometimes they make a mistake and regret it : they've lost the way to restore the file by refusing using the trash
See the paradox : the trash is a functionality that people want but refuse to use. It could be the sign that the functionality has usability drawbacks and that it should be improve...

Moreover people doesn't want to empty the trash in real life : why would they enjoy doing it on their computer ?!

The improvement could consist in automatically suppressing the files in the trash can after a couple of days. Of course it should be optional

Some people are using cron a rm -rf ~/.Trash/* but that is not optimal
See also that Python script http://www.logfish.net/pr/autotrash/

See also
http://open-source.ecchi.ca/?voir=articles/dont_care_about_trash
http://en.opensuse.org/OpenSUSE_GNOME_post-10.3_ideas#Misc

Thanks
Comment 1 A. Walton 2010-05-23 15:25:28 UTC

*** This bug has been marked as a duplicate of bug 149572 ***