9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Replacement for find
Date: Wed, 30 Sep 2015 09:57:26 -0500	[thread overview]
Message-ID: <CAGGHmKFijY=VfT1KCiqXgFROQfVp1nd2ukc3TT9EsY9YV_BNmw@mail.gmail.com> (raw)
In-Reply-To: <8fb44c5359889dbe523888b5451eeb4c@brasstown.quanstro.net>

Somewhat late to the party, but I use the following in my profile:

fn find {du -a $* |awk '{print $2}'}

http://plan9.bell-labs.com/sources/contrib/stallion/profile

On Wed, Sep 30, 2015 at 8:20 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> On Wed Sep 30 01:12:36 PDT 2015, charles.forsyth@gmail.com wrote:
>
>> On 30 September 2015 at 09:01, Wolfgang Helbig <helbig@mailbox.org> wrote:
>>
>> > But I consider it ugly, to ask for the disk usage if you just want to
>> > recursively list all files.
>> >
>>
>> It probably is not ideal, even when the circumlocution is hidden in a
>> script.
>> Perhaps find's syntax and conventions could be improved, though?
>
> 9atom has a relative of andrey's find.  it takes very few options.
> the -d and -D options are not easily duplicated with du.
>
> ; man find
>
>      FIND(1)                                                   FIND(1)
>
>      NAME
>           find - recursively list files.
>
>      SYNOPSIS
>           find [ -1Ddfq ] dir ...
>
>      DESCRIPTION
>           List each argument.  If the argument is a directory recur-
>           sively list it's contents.  The default is to list the cur-
>           rent directory.  Specifying -d prints only directories, -D
>           prints only files, -f supresses warnings, while -q supresses
>           quoting the output for rc(1). With -1, mount points will not
>           be traversed.
>
>      SOURCE
>           /sys/src/cmd/find.c
>
>      SEE ALSO
>           du(1)
>
>      BUGS
>           Feeping creaturism.
>
>
> - erik
>



  parent reply	other threads:[~2015-09-30 14:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  8:01 Wolfgang Helbig
2015-09-30  8:09 ` lucio
2015-09-30  8:11 ` Charles Forsyth
2015-09-30  8:23   ` hiro
2015-09-30  8:27     ` lucio
2015-09-30 10:34       ` hiro
2015-09-30  9:33     ` Wolfgang Helbig
2015-09-30  9:58       ` Aram Hăvărneanu
2015-09-30 10:41         ` Wolfgang Helbig
2015-09-30 10:45           ` hiro
2015-09-30 10:07       ` Steve Simon
2015-09-30 10:55         ` Mark van Atten
2015-09-30 11:25           ` Wolfgang Helbig
2015-09-30 13:20   ` erik quanstrom
2015-09-30 14:32     ` arnold
2015-10-01  0:06       ` sl
2015-09-30 14:57     ` Steven Stallion [this message]
2015-09-30 10:31 ` Brantley Coile
  -- strict thread matches above, loose matches on Subject: below --
2015-09-30  6:26 Wolfgang Helbig
2015-09-30  6:39 ` Alexander Kapshuk
2015-09-30  6:54 ` Mark van Atten
2015-09-30  7:39   ` hiro

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='CAGGHmKFijY=VfT1KCiqXgFROQfVp1nd2ukc3TT9EsY9YV_BNmw@mail.gmail.com' \
    --to=sstallion@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).