Default size unit looks weird

[sergeevabc]

Windows 7 x64, g 0.30.0

$ du -b *
889     gsr1.crt
525     r4.crt
657     we2.crt

$ g -1 --size
889.0 B gsr1.crt
525.0 B r4.crt
657.0 B we2.crt

Why is 0 needed here? How can it be, say, 657.2 B? I guess not.
And to get a more intelligible look, you need to spend effort lengthening the command.

$ g -1 --size --size-unit b
889 B gsr1.crt
525 B r4.crt
657 B we2.crt

[Equationzhao]

Hi, thanks for your feedback and for the clear comparison!

You're right — showing a decimal for bytes (like 889.0 B) doesn't really make sense, since you can't have a fraction of a byte. This is something I overlooked, and it's more intuitive to display bytes as whole numbers.

I'm planning to update the default behavior so that:

Byte units will always be shown as integers (e.g., 657 B)
Only larger units (like KB, MB, etc.) will use decimals for better readability
Would this approach work for you?

Thanks again for pointing this out!