How do you manage your ".Trash" folder? Who is in charge of deleting it's content? Do you do it periodically or based on some other event?
Stop Using `rm` in Bash. Use `del`
31–40 of 76 posts
Re: Stop Using `rm` in Bash. Use `del`
#32This is another example that shows that Bash (and similar shells) should not be used for scripting. It's great for the command line, but for scripting there are much better, cleaner, faster and safer alternatives.
Please elaborate :)
Re: Stop Using `rm` in Bash. Use `del`
#33My “alternative” to rm is to use mv directly. I just mv files aside whenever I am not 100% confident they are safe/ready to delete permanently.
Personally I’m not a fan of shell environment customizations like this because they are often fragile and may vary between systems. I like to know exactly what commands I’m executing.
Re: Stop Using `rm` in Bash. Use `del`
#34Earlier quoted context omitted.
Now let's delete them after roughtly 30 days: alias del="mv -t ~/.Trash/ ; find ~/.Trash/ -mtime +30 -exec rm {} \;"
This is not fine, as deleting a small file can be very long if there's a large file to be deleted in the trash.
Yeah running the delete in the user's crontab (i.e. in the background and on a schedule) would be a better option IMO.
Re: Stop Using `rm` in Bash. Use `del`
#35This is another example that shows that Bash (and similar shells) should not be used for scripting. It's great for the command line, but for scripting there are much better, cleaner, faster and safer alternatives.
There's plenty of good reasons not to use shellscript, but someone not knowing the difference between "$@" and $* isn't one of them. This is prominently documented in Bash's documentation: https://www.gnu.org/software/bash/manual/html_node/Special-P...
Re: Stop Using `rm` in Bash. Use `del`
#36This is another example that shows that Bash (and similar shells) should not be used for scripting. It's great for the command line, but for scripting there are much better, cleaner, faster and safer alternatives.
What? No, come on. You can’t extrapolate “someone didn’t read the manual” to “don’t use shell scripting”.
Re: Stop Using `rm` in Bash. Use `del`
#37Earlier quoted context omitted.
Even simpler: alias del="mv -t ~/.Trash/"
Now let's delete them after roughtly 30 days: alias del="mv -t ~/.Trash/ ; find ~/.Trash/ -mtime +30 -exec rm {} \;"
This fails on directories, as the -r switch was not included:
mkdir foo; del foo
EDIT: See also neighbor comment about appending filenames!
Re: Stop Using `rm` in Bash. Use `del`
#38Re: Stop Using `rm` in Bash. Use `del`
#39For Linux users: also look into the trash-cli [1] package, which complies with the FreeDesktop.org trash specification and remembers the original path, etc. so that trash items can be restored even with filename collisions. Then it's trash-put my_file.txt [1] https://github.com/andreafrancia/trash-cli
Until at least an year ago, the Ubuntu version (and likely, the upstream on), wouldn't work on certain filesystems.
I'm not sure about the current state, but one needs to test is very carefully before using it.
Re: Stop Using `rm` in Bash. Use `del`
#40For Linux users: also look into the trash-cli [1] package, which complies with the FreeDesktop.org trash specification and remembers the original path, etc. so that trash items can be restored even with filename collisions. Then it's trash-put my_file.txt [1] https://github.com/andreafrancia/trash-cli
Until at least an year ago, the Ubuntu version (and likely, the upstream on), wouldn't work on certain filesystems. I'm not sure about the current state, but one needs to test is very carefully before using it.
Which filesystem were you using when you encountered trouble with it? What happened when you tried to use it? Did it warn you about the filesystem issue? Did it delete rather than trash?