From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] lsr
Date: Fri, 5 Sep 2008 12:57:05 -0400 [thread overview]
Message-ID: <2255d1f4e477024e3cb6cc63f0fe3761@9srv.net> (raw)
In-Reply-To: <129570.47211.qm@web56201.mail.re3.yahoo.com>
There's also 'walk' by Dan Cross, in /n/sources/contrib/cross/walk.c.
Lsr's faster (bufio?), but I like walk's depth-limiting switch (and it
sounds like you might like the quoting switch).
Dan also did sor ("streaming or") to apply various tests to files. The
two in combination do very well for replacing 99% of find usage. See
Dan's posts here:
http://9fans.net/archive/2002/10/653
http://9fans.net/archive/2002/10/655
I see no reason sor wouldn't work with lsr, too. Also in Dan's contrib.
I can't particularly say why either one's not in the distribution. First
order, I assume the authors never submitted them for inclusion.
Anthony
prev parent reply other threads:[~2008-09-05 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 15:08 gas
2008-09-05 16:57 ` a [this message]
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=2255d1f4e477024e3cb6cc63f0fe3761@9srv.net \
--to=a@9srv.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).