Provide a way to show size of sub-elements of a given folder

[jonhoo]

One of the most common use-cases for du -hs by far for me (and also what dust caters to), is to do du -hs * to find the largest directories in a given directory (usually the current one). It doesn't seem like diskus can currently operate in that mode? It'd be awesome if that kind of "tell me what's large" quick-n-dirty mode could be supported somehow!

[sharkdp]

I was not planning to turn this into a full-blown replacement for du, but that is indeed also my most common use-case.

What about changing the usage to

diskus [path]...

where diskus would just show the total size of the current directory, but diskus path1 path2 would show the total size for each path? The latter could simply be used with diskus *.

[jonhoo]

That seems perfect! I think it'd also be handy for the resulting list to be sorted by size, not by the order of the arguments, but with that that's pretty much all I'd need!

[polyzen]

Could just pipe it through sort.

[jonhoo]

@polyzen yup, you can always do that, but I'd argue that since it's by far the most common use-case, it seems reasonable for that to be the default :) That is also what dust does.

[kpcyrd]

I usually use du -sch * which lists the size of each file/folder and the total size of all combined. This would be really useful to have.

[joeshaw]

I tend to use du -h -d 1 over du -sh * for this, because it only lists directories.

It is sometimes nice to use a greater depth, like when trying to track down an unknown, particularly large subdirectory. So, at the risk of feature creep, it'd be nice to have summaries of arbitrary depth.

[rNoz]

My main use case is exactly like @kpcyrd and @polyzen: per directory and file, total size of every listed file and output piped to sort -h.

[mw55309]

Hello, was this ever implemented?

[busfahrer]

+1, from reading the description of this tool I assumed that's what it actually was - my 90% use case of for du is du -s * | sort -n. Would love to use diskus' great performance for that use case!