From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <Pine.BSI.4.64.0912290758490.5454@malasada.lava.net>
References: <20091228230510.GA25423@machine>
	<Pine.BSI.4.64.0912290758490.5454@malasada.lava.net>
From: Rob Pike <robpike@gmail.com>
Date: Wed, 30 Dec 2009 07:16:57 +1100
Message-ID: <7359f0490912291216o4d6e857ei31f054598db0d1a2@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] du and find
Topicbox-Message-UUID: b395d4b8-ead5-11e9-9d60-3106f5b1d025

The 'g' is unnecessary.

-rob

On Wed, Dec 30, 2009 at 4:59 AM, Tim Newsham <newsham@lava.net> wrote:
>> It is suggested to use
>> =A0 du -a | awk '{print $2}'
>> instead of find. But what if filename contains spaces? For example if
>> file is named "foo bar" then awk will output "foo" only.
>
> What about
>
> =A0 du -a | sed 's/^[0-9]*<tab>//g'
>
> no loss on spaces in filenames.
> no loss on tabs in filenames.
>
> Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
>
>