File sizes with -b option difficult to read without thousands delimiter (comma, period)

[AGI-chandler]

It would help to add the thousands delimiter when using -b option.  I think the code could even automatically use a comma or period based on the system's locale settings...
Thanks

[zevv]

I like the readability of thousands separators, but I'm not too fond of them because it makes parsing ducs output much harder from scripts or other tools.

@l8gravely Opinions on this?

[l8gravely]

>>>> "Ico" == Ico Doornekamp ***@***.***> writes: I like the readability of thousands separators, but I'm not too fond of them because it makes parsing ducs output much harder from scripts or other tools. @l8gravely Opinions on this?

I think we could add a -H (human) or -c (commified) flag to 'duc info -b -H ...' to show the data in a human readable format. Hmm... maybe -B is the better option, where -b is bytes, but -B is bytes in human readable format? Shouldn't be too hard to add into the code. Haven't looked though.

[zevv]

Ah, -B is not bad; the change is trivial, I'll put it in.

[AGI-chandler]

cool, thanks guys... would this only be for info subcommand or would work for the rest as well?

[zevv]

Bah, I hate naming. How should we call the longopt, -b is for --bytes, so -B will be for what?