mirror of
https://github.com/bootandy/dust.git
synced 2026-06-08 11:29:05 +03:00
[GH-ISSUE #326] dust in a deleted/missing directory outputs a different dir
#142
Assignees
zhus (Sergey Zhukov)
Clear assignees
zhus (Sergey Zhukov)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bootandy/archived-dust#142
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lesleyrs on GitHub (May 7, 2023).
Original GitHub issue: https://github.com/bootandy/dust/issues/326
I was expecting it to give an error, but instead it shows a completely different directory (in my case it's the default dir, not sure exactly what it's doing). This is on windows.
Thx for this tool btw, helped me clean my ssd as the official windows tools don't show hidden files which is fair I guess.
@bootandy commented on GitHub (May 7, 2023):
Are you running dust in the directory after you have deleted the directory ?
@lesleyrs commented on GitHub (May 7, 2023):
Yes, by deleting it in file explorer instead of the terminal. I think this causes it to output the default starting directory, I'd prefer just an error message.
@bootandy commented on GitHub (May 8, 2023):
I'm not sure that's going to be possible.
what happens if you run dust on a directory that doesn't exist in windows:
dust C:\THIS_DOES_NOT_EXIST/\
?
@lesleyrs commented on GitHub (May 8, 2023):
If it's not going to work feel free to close, it's not a big deal but would just be a little improvement.
It shows