Bug#786564: Please add option for extra precision human readable output

2015-06-11 Thread Goswin von Brederlow
On Fri, May 22, 2015 at 05:37:04PM -0400, Michael Stone wrote:
 On Fri, May 22, 2015 at 11:24:03PM +0200, Goswin von Brederlow wrote:
 when using df -h the output will use the largest unit that doesn't
 have a leading 0. This often results in quite imprecise output, e.g.
 1.1T or 1.8G. It would be nice if instead it cout use the smallest
 unit that use 4 or less characters (maybe even 5 if a . is involved).
 
 I'm struggling to think of a use case that requires 4 digits of precision on
 a terabyte filesystem. If you need to know the exact size, then get the size
 in bytes. Otherwise, it's probably close enough.
 
 Mike Stone

4 chars for the number, which would only be 1-2 digits of precision.
As in 11.7G instead of 12G or 1750M instead of 1.8G. 4 digits of
precision would indeed be too much.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#786564: Please add option for extra precision human readable output

2015-06-11 Thread Michael Stone

On Thu, Jun 11, 2015 at 11:49:42AM +0200, Goswin von Brederlow wrote:

On Fri, May 22, 2015 at 05:37:04PM -0400, Michael Stone wrote:

On Fri, May 22, 2015 at 11:24:03PM +0200, Goswin von Brederlow wrote:
when using df -h the output will use the largest unit that doesn't
have a leading 0. This often results in quite imprecise output, e.g.
1.1T or 1.8G. It would be nice if instead it cout use the smallest
unit that use 4 or less characters (maybe even 5 if a . is involved).

I'm struggling to think of a use case that requires 4 digits of precision on
a terabyte filesystem. If you need to know the exact size, then get the size
in bytes. Otherwise, it's probably close enough.

Mike Stone


4 chars for the number, which would only be 1-2 digits of precision.
As in 11.7G instead of 12G or 1750M instead of 1.8G. 4 digits of
precision would indeed be too much.


We already have at least two digits of precision and often three. Your 
1750M *is* 4 digits of precision. And you said maybe even 5 if a . is 
involved. But I'll restate to avoid the quibble: I'm struggling to 
think of a use case that requires 3 digits of precision on a terabyte 
filesystem. If you need to know the exact size, then get the size in 
bytes. Otherwise, it's probably close enough.


ike stone


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#786564: Please add option for extra precision human readable output

2015-05-22 Thread Michael Stone

On Fri, May 22, 2015 at 11:24:03PM +0200, Goswin von Brederlow wrote:

when using df -h the output will use the largest unit that doesn't
have a leading 0. This often results in quite imprecise output, e.g.
1.1T or 1.8G. It would be nice if instead it cout use the smallest
unit that use 4 or less characters (maybe even 5 if a . is involved).


I'm struggling to think of a use case that requires 4 digits of 
precision on a terabyte filesystem. If you need to know the exact size, 
then get the size in bytes. Otherwise, it's probably close enough.


Mike Stone


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#786564: Please add option for extra precision human readable output

2015-05-22 Thread Goswin von Brederlow
Package: coreutils
Version: 8.21-1.2
Severity: wishlist
File: /bin/df

Hi,

when using df -h the output will use the largest unit that doesn't
have a leading 0. This often results in quite imprecise output, e.g.
1.1T or 1.8G. It would be nice if instead it cout use the smallest
unit that use 4 or less characters (maybe even 5 if a . is involved).

So the output would go

0 -     0 -  
10.0k - k  or  10.00k - k
10.0M - M  10.00M - M
10.0G - G  or  10.00G - G

and so on. Extra points for adding a --precision=num chars instead
of hardcoding 4/5 chars.

MfG
Goswin

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armel

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages coreutils depends on:
ii  libacl1  2.2.52-1
ii  libattr1 1:2.4.47-1
ii  libc62.19-17
ii  libselinux1  2.3-1

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org