From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Oooops...where is ls -R gone?
Date: Fri, 17 Aug 2001 08:49:26 +0000 [thread overview]
Message-ID: <3B7C2B14.9E4305A0@null.net> (raw)
In-Reply-To: <20010816013325.0875A19B08@mail.cse.psu.edu>
dmr@plan9.bell-labs.com wrote:
> No, [find(1)] was there, in 6th and 7th editions and thereafter.
> A xenograft from USG, but there, albeit with a BUGS section
> saying "The syntax is painful."
Unfortunately, there has never (to my knowledge) been a really
satisfactory tree walker in any version of UNIX. Even "xargs",
which one would think would be debugged by now, fails when
there are spaces, ampersands, etc. in leaf names. I know of
several attempts to provide library or kernel support for tree
walking; the reason none were specified for POSIX <dirent.h>
(which I was the main proponent for) was that none of them had
worked well enough in practice to make a convincing case that
they should be standardized. I think this is a solvable problem
for which a really good solution would eventually attract users.
next prev parent reply other threads:[~2001-08-17 8:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 1:32 dmr
2001-08-17 8:49 ` Douglas A. Gwyn [this message]
2001-08-17 12:11 ` Boyd Roberts
2001-08-17 16:02 ` Dan Cross
2001-08-21 16:32 ` Jon Snader
2001-08-21 19:04 ` Re[2]: " Matt
2001-08-21 20:29 ` Jon Snader
2001-08-22 8:21 ` Caldera source [ was Re: Re[2]: [9fans] Oooops...where is ls -R gone? ] Aharon Robbins
2001-08-24 17:01 ` [9fans] Re: Caldera source Ralph Corderoy
2001-08-21 22:30 ` [9fans] Oooops...where is ls -R gone? Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 12:12 rog
2001-08-09 2:33 anothy
2001-08-08 9:38 forsyth
2001-08-08 7:27 pac
2001-08-08 7:49 ` Boyd Roberts
2001-08-08 8:17 ` pac
2001-08-15 17:11 ` Boyd Roberts
2001-08-15 18:02 ` Dan Cross
2001-08-15 23:22 ` Boyd Roberts
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=3B7C2B14.9E4305A0@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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).