9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Replacement for find
Date: Wed, 30 Sep 2015 11:07:41 +0100	[thread overview]
Message-ID: <2dbef77b03e145df443c861f471f434b@quintile.net> (raw)
In-Reply-To: <5F9B8349-6B7F-4213-84FF-50D65B5159E6@mailbox.org>


> In Plan 9 a command is needed, that lists recursively all files.
> Not more and not less.
> The du(1) command offers too much.
> I do not want to list the disk usage!

I don't feel this need, though you obviously do.
You could try:

	#!/bin/rc

	du $* | while(s=`{read})
		echo $2

NB: don't use sed or awk, they don't understand the shells
quoting convention for filenames containing frogs.

Re: usage

Rather than doing
	B `{find . --name '*.[ch]' --print}

I do this:

	du -a | grep '\.[ch]$'

find the file I am interested in in the list and plumb it,
I guess its just personal taste.

Plan9 is different and somtimes it needs a different approach.

-Steve



  parent reply	other threads:[~2015-09-30 10:07 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 [this message]
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
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=2dbef77b03e145df443c861f471f434b@quintile.net \
    --to=steve@quintile.net \
    --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).