-
Notifications
You must be signed in to change notification settings - Fork 24
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
No updates until godu finishes full walk #14
Comments
I was thinking about printing some warning that With the second suggestion I'll first need to capture the full path of each file. Right now the root file has exactly the same name as CLI argument and every other file is relative to it.. I'm not sure how helpful would be the relative path. |
A single line at the very top / bottom would be nice to show additional information of #18, e.g. "marked files", "marked file size" (so you know how much space can be freed), .. |
Yes, I was thinking the same. I was planning to put absolute path in it, but marked file size would be a great thing as well. |
@sathishvj are you happy with #18 functionality? Or did you mean full |
Presently you've given only a single line warning. What I was suggesting was using something like https://github.com/gosuri/uilive (single line update of files being processed) or like this https://github.com/gosuri/uiprogress. Maybe similar to this http://masterex.github.io/archive/2011/10/23/progressbar.gif, but instead of showing % complete, you show how many files/folders traversed followed by the name of current file/folder being traversed. Additionally if there is a -l option for verbose, it could be a full listing with probably a separator of choice. Users could then pipe this to grep, sed, txt file, etc. Just suggestions you could consider, but thank you anyways for doing the project and taking suggestions. |
Understand now. I think that the first suggestion is great, The The second suggestion is very close to result of directly calling |
For windows users, there isn't a good du. So this could help. And since it is go, it should work without issues in Windows also. |
Once godu is run, there is no update for a while on a big volume.
My suggestion would be to use a one line, in place updating message of what's happening.
Additionally, you could give a cmd line option to list each line output so that somebody can pipe it to a txt file if they want to see it differently.
The text was updated successfully, but these errors were encountered: