<br><br><div class="gmail_quote">On Sat, Aug 15, 2009 at 9:34 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On Fri, Aug 14, 2009 at 11:38:22AM -0600, David Farber wrote:<br>
><br>
> Spaces in file names are natural to Mac users (I'm a Mac user) but,<br>
> in my opinion, they are best left to the "casual users" and the GUI<br>
> side of the OS. If I'm working with documents in the regular GUI<br>
> apps (Text Edit, Word, the Finder, etc) I will use spaces in file names.<br>
><br>
> But if I am on the "unix" side of the OS (using Terminal, using<br>
> emacs, using unix tools, doing development, etc) I do not use spaces<br>
> in file names.<br>
><br>
> My preference would be to remove spaces from the file names in the<br>
> Mac OS subtree.<br>
<br>
</div>If you are working from a Terminal, try something like this to scan<br>
for all C source and header files that contain the string 'foobar':<br>
<br>
$ find 'Mac OS' -name '*.[ch]' -exec grep -l foobar {} \;<br>
</blockquote><div><br></div><div>If there are spaces in the filename then you need to put quotes around the file name expansion, i.e.</div><div><br></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">$ find 'Mac OS' -name '*.[ch]' -exec grep -l foobar "{}" \;</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "></span> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Dave<br>
<br>
</blockquote></div><br>