From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] walk
Date: Thu, 24 Jul 2003 11:21:13 +0200 [thread overview]
Message-ID: <012701c351c4$eddf9a80$b9844051@insultant.net> (raw)
In-Reply-To: <001901c351c2$68c21140$2a8be793@gli.cas.cz>
> term% walk ./ grep -n aint *.idx
the *.idx get expanded immediately and that file doesn't exist in the directory
walk has chdir'd to, which it looks like it's doing. i can even find any doc
for walk, nor the source.
but it looks like:
walk dir command [ args ... ]
and it uses chdir.
next prev parent reply other threads:[~2003-07-24 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 9:03 pac
2003-07-24 9:21 ` boyd, rounin [this message]
2003-07-25 6:36 pac
2003-07-25 13:59 ` Dan Cross
2003-07-25 14:07 ` Fco.J.Ballesteros
2003-07-25 14:16 ` Charles Forsyth
2003-07-25 15:31 ` Dan Cross
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='012701c351c4$eddf9a80$b9844051@insultant.net' \
--to=boyd@insultant.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).