public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] coreutils patch for 'ls -l' of GB files
Date: Sun, 25 Apr 2004 16:36:11 -0700	[thread overview]
Message-ID: <20040425233611.GA20867@phaenix.haell.com> (raw)
In-Reply-To: <20040424215503.GC14678@lakedaemon.net>

[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]

On Sat, 2004-04-24, 17:55:03 -0400, in <20040424215503.GC14678@lakedaemon.net>, Jason Cooper <gentoo@lakedaemon.net> wrote:
> Daniel Drake (dsd@gentoo.org) scribbled:
> > Jason Cooper wrote:
> > 
> > >So my question for you guys is this:  Should I submit this to the
> > >coreutils owner?  It's stupid simple, literally a one-line patch.  I'd
> > >make it a command line option, but I think they left it hard-coded for a
> > >reason...  

Probably the same reason programmers used two-digit years for so long.
"This will work for now. I'll fix it later, before it becomes a
problem." What was the largest hard drive available in 1985? Files
larger than 95 GB were never going to happen...

> > If you make your new behaviour default, you may break many peoples scripts 
> > that expect the size column to be 8 characters long.

Files larger than 99999999 bytes will also break scripts which depend
on an 8-character size column.

> > My opinion is that your modification should become accessible only through 
> > a non-default commandline parameter.
> 
> Agreed, would an "auto-adjusting width" be a worthwhile endevour?  It
> seems kind of pointless to add a commandline option just to increase the
> column width two characters, not to mention temporary (tera/peta-byte size
> files?).  A more robust solution would be for the option to allow the
> column width to shrink and grow based on the largest file in the list.

Frankly, an "auto-adjusting width" should probably be the default. It
should not break anything which grabs the fifth space-separated field,
and anything which grabs characters 35 through 42 is broken, anyway.

Thinking from another point of view, the output from `ls -l` is intended
for human consumption. Robust scripts which need to determine the size
of a file (should) use `stat -c %s`.

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2004-04-25 23:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24 15:50 [gentoo-dev] coreutils patch for 'ls -l' of GB files Jason Cooper
2004-04-24 17:09 ` Daniel Drake
2004-04-24 21:55   ` Jason Cooper
2004-04-24 21:53     ` Daniel Drake
2004-04-25 23:36     ` Drake Wyrm [this message]
2004-04-29  4:54   ` Mike Frysinger
2004-04-29 12:32     ` Jason Cooper
2004-05-03 18:56       ` Mike Frysinger
2004-05-03 20:52         ` Peter Ruskin
2004-04-25 13:43 ` Christian Birchinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040425233611.GA20867@phaenix.haell.com \
    --to=wyrm@haell.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox