comment on

Honestly, though, I'd skip du, and just use cog's FileSys::DiskUsage module. It wouldn't be as short, but it'd be, um, a bit more readable ;-)

#! /usr/bin/perl
use strict;
use warnings;
use Filesys::DiskUsage qw(du);
use Sort::Key qw(ikeysort);

my @files = @ARGV ? @ARGV : glob '*';
my %sizes = du(
               {
                   'make-hash' => 1,
                   'recursive' => 0,
                   'sector-size' => 1024,
               }, @files);

@files = ikeysort { $sizes{$_} } keys %sizes;

my %config = ( human => 1, 'truncate-readable' => 2 );
printf "%8s %s\n",
    Filesys::DiskUsage::_convert($sizes{$_}, %config),
    $_ for @files;
[download]

But, that's just me. (And look at all the other cool things you can do with Filesys::DiskUsage, or even the output format!

In reply to Re: du -h, sorted by Tanktalus
in thread du -h, sorted by bellaire

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks