-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug Report] Error: No such file or directory (os error 2) because of "broken symbolic link" #124
Comments
Thanks for a lot for letting me know. The problem seems to be that it will completely fail if one root path on the command-line cannot be read. So
|
yeah, I have two solutions in mind:
Maybe provide a flag so dua ignores it or prints it. |
…lts. (#124) Previously it would fail completely without printing anything.
…ad. (#124) Note that there can still be improvements in indicating which path failed. Also it will happily show an empty user interface in case all input paths are not readable.
Thanks for sharing! I think I have found a solution that works well with how these errors are usually handled. |
…#124) See [their respective release](https:/Byron/trash-rs/releases/tag/v2.1.2).
This is not always happening as you can see, depending on the keywords I pass, so I analysed all the file types in the list and noticed some files are "broken symbolic link to..."
So
The text was updated successfully, but these errors were encountered: