Open wparad opened 2 years ago
How to reproduce this issue?
I'm almost positive it was happening when running safe-rm CHILD_DIRECTORY -rf
or safe-rm ./CHILD_DIRECTORY -rf
, but I often would only find out ~10 minutes later that it happened when doing development that the directory I was in was no longer available. Or maybe it was putting the -rf
first that caused the problem. One of these was the issue.
If you run this executable occasionally it will decide to delete the current working directory as well as the target.
I'm almost positive it was happening when running
safe-rm CHILD_DIRECTORY -rf
orsafe-rm ./CHILD_DIRECTORY -rf
, but I often would only find out ~10 minutes later that it happened when doing development that the directory I was in was no longer available. Or maybe it was putting the-rf
first that caused the problem. One of these was the issue.