When you release shift too early

4 Replies 
$ diff /tmp/list.txt ~/Desktop/list.txt
$ rm !!;1
rm: cannot remove `diff': No such file or directory
bash: 1: command not found

The semi-colon should’ve been a colon, which selects just word 1 from the previous line. Instead, I deleted everything. Of course that’s what I intended to do, you piece of crap.

I usually use trash-cli and don’t bother deleting most files in /tmp. duplicity helped me get my files back, thankfully.

While on this: freedesktop.org’s trash specification leaves a few things to be desired:

  • Consistent support for trashing on mounts besides the one containing your home directory.
  • Automatic erasing of old files on space depletion.

Follow me on Twitter for stuff far more interesting than what I blog.

No related posts.

  • I’m not sure to have understand your comment about “Consistent support for trashing on mounts besides the one containing your home directory”. Could you explain to me what is the problem you see in the Trash Spec?

    Thanks

  • I’m not sure to have understand your comment about “Consistent support for trashing on mounts besides the one containing your home directory”. Could you explain to me what is the problem you see in the Trash Spec?

    Thanks

  • Hi, Andrea. I just meant that the Trash specification leaves open a large number of decisions for the implementation, particularly with regard to top directory trashing on non-home mounts. The number of conditionals in the “Trash directories” section is large. Some of these are understandable, but others appear to be superfluous, such as the existence of both .Trash and .Trash-$uid.

  • Hi, Andrea. I just meant that the Trash specification leaves open a large number of decisions for the implementation, particularly with regard to top directory trashing on non-home mounts. The number of conditionals in the “Trash directories” section is large. Some of these are understandable, but others appear to be superfluous, such as the existence of both .Trash and .Trash-$uid.