Recursive Find from Command Line

By  on  

Probably a dozen times a day I need to search any given project for specific code keywords.  Most of the time it's within a specific project but then there are times where I don't remember which directory or project the specific text is -- from my blog to my many Mozilla projects, I have code all over my local machine and it's oftentimes difficult to find something I need.

Most of the time I need to open my text editor and have it do the hard work of what I'm looking for but that's probably not efficient -- a more efficient tool would come from command line and thanks to CommandLineFu.com, I found the perfect command:

# Search all ".js" files for "debounce"
# Spits out file path, line number, and snippet where string appears
find . -name "*.js" -exec grep -in -H "debounce" {} \;

The command above searches files recursively to find the desired string, outputting the source file and the text which the string occurs in!

Recent Features

Incredible Demos

  • By
    Unicode CSS Classes

    CSS class name structure and consistency is really important; some developers camelcase classnames, others use dashes, and others use underscores.  One thing I've learned when toying around by HTML and CSS class names is that you can actually use unicode symbols and icons as classnames.

  • By
    Translate Content with the Google Translate API and JavaScript

    Note:  For this tutorial, I'm using version1 of the Google Translate API.  A newer REST-based version is available. In an ideal world, all websites would have a feature that allowed the user to translate a website into their native language (or even more ideally, translation would be...

Discussion

  1. Vladimir

    Recently I’m using:

    grep 'term' -r ./

    I think grep also has an option to filter on file extension too and I use it sometimes, but I don’t know it by heart.

  2. The output on this looks pretty must the same as with the functionality already built into grep using the -r and --include flags. I also tend to add the -n flag to output the line numbers as well. I believe this should line be equivalent.

    grep -rin --include="*.js" "debounce" .
  3. The find trick was one I learned at university in the 1990s, when most greps didn’t have the recursive flag. My vague recollection is that GNU grep introducing -r gave much of the competition a bit of a kick up the arse, and now it’s fairly common, but the find trick is still useful on older or more obscure Unix platforms…

  4. Jeremy

    Pretty sure you have a typo in there. “*.[js]” means “*.j” or “*.s”, which is likely to find nothing.

    • Good point — left some testing in there. Updated!

  5. Check out Ack (http://beyondgrep.com/why-ack/).

    ack debounce
    • Oh, you were filtering for JavaScript files only. That’s as easy as

      ack debounce --type=js

      :-)

  6. Isaiah

    Wasn’t able to execute this through the command line: Err find: missing argument to `-exec'

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!