-
Notifications
You must be signed in to change notification settings - Fork 112
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
Skip through single parent directory in interactive mode #110
Comments
Thanks for sharing :)! I like the idea of generalizing the 'skip single-parent roots', which would solve the startup issue of showing something people probably aren't very interested in, while also preventing people from having to skip through mostly empty directories. If that auto-skipping happens, showing some information would definitely be useful. Allow me a few questions though:
|
No, it should behave just like normal. GitHub has a similar behavior for skipping single parent directories, however it only does so when you open subdirectories, not when you go upwards.
That's a good question, I didn't think about it. I will answer it in the next question.
Ideally it should work "transparently", i.e. it should behave like the user supplied subdirectories as arguments. But since #82 has not been implemented yet, transparently skipping stuff will cause some inability. In that case, dua-cli can just "fast-forward" its initial root to the most meaningful subdirectory. I'm not sure what do you mean by "generalizing", here is how it may work:
|
…orking dir (#110) This makes it seem like the user started the directory walk directly in the given directory, which is more intuitive than the previous approach only showed the given directory as top-level directory. Note that this change only affects invocations like `dua <dir>` or `dua i <dir>`.
IMHO this is as much done as it makes sense to do. |
Thanks for the reminder! |
If given a single directory as parameter in interactive mode (e.g.
dua i Developer
), dua-cli's initial state will be like:However there's nothing useful here, the total usage is available at the bottom and the percentage will certainly be 100%. What users expect is more likely this (e.g.
dua i Developer/*
):(The entries difference is because we are not counting the parent directory, but that should not matter.)
There should a badge or something like that to inform the users dua-cli has skipped through the parent directory.
If dua-cli can skip all single parent directory, that will be more awesome.
Let's suppose we have the following file structure:
It is ideal that
dua i a
equalsdua i a/b/c/*
.The text was updated successfully, but these errors were encountered: