Skip to content

[FEAT] Byte units should always be shown as integers #236

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

Open
Equationzhao opened this issue May 21, 2025 · 0 comments
Open

[FEAT] Byte units should always be shown as integers #236

Equationzhao opened this issue May 21, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@Equationzhao
Copy link
Owner

Discussed in #234

Originally posted by sergeevabc May 9, 2025
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 Equationzhao changed the title Default size unit looks weird Byte units will always be shown as integers May 21, 2025
@Equationzhao Equationzhao changed the title Byte units will always be shown as integers [FEAT] Byte units should always be shown as integers May 21, 2025
@Equationzhao Equationzhao added the enhancement New feature or request label May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant