<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Keith Hellman wrote:
<blockquote cite="mid20050105145831.GA6685@mcprogramming.com"
type="cite">
<pre wrap="">On Wed, Jan 05, 2005 at 06:46:58AM -0700, Collins Richey wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, 4 Jan 2005 22:13:15 -0700, Jeff Cann <a class="moz-txt-link-rfc2396E" href="mailto:j.cann@isuma.org"><j.cann@isuma.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
<snip>
$ find . -exec grep 'string to find' {} \; -print
</snip>
</pre>
</blockquote>
<pre wrap="">Always a fan of simplicity, what does the find expression give you
that this does not?
grep -R 'string to find' *
</pre>
</blockquote>
<pre wrap=""><!---->The difference would be that the grep invokation would not find a
target file if it were in a 'hidden' directory of the invokation
directory. The '*' would be expanded by shell and miss it.
grep -R 'string to find' .
would, AFAICT, produce the same results as Jeff's find.
Sorry, it was a really nit-picky thing. But then nit-picky is what I do
best :^)
</pre>
</blockquote>
<br>
Please everyone, if you're not using regular expressions, use fgrep.<br>
<br>
(talk about nit-picky)<br>
<br>
</body>
</html>