Recursive Find from Command Line
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!
![An Interview with Eric Meyer]()
Your early CSS books were instrumental in pushing my love for front end technologies. What was it about CSS that you fell in love with and drove you to write about it?
At first blush, it was the simplicity of it as compared to the table-and-spacer...
![Camera and Video Control with HTML5]()
Client-side APIs on mobile and desktop devices are quickly providing the same APIs. Of course our mobile devices got access to some of these APIs first, but those APIs are slowly making their way to the desktop. One of those APIs is the getUserMedia API...
![Using jQuery and MooTools Together]()
There's yet another reason to master more than one JavaScript library: you can use some of them together! Since MooTools is prototype-based and jQuery is not, jQuery and MooTools may be used together on the same page.
The XHTML and JavaScript
jQuery is namespaced so the...
![Jack Rugile’s Favorite CodePen Demos]()
CodePen is an amazing source of inspiration for code and design. I am blown away every day by the demos users create. As you'll see below, I have an affinity toward things that move. It was difficult to narrow down my favorites, but here they are!
Recently I’m using:
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.
The output on this looks pretty must the same as with the functionality already built into grep using the
-rand--includeflags. I also tend to add the-nflag to output the line numbers as well. I believe this should line be equivalent.https://vivekragunathan.wordpress.com/more-resources/cmd-line-sucks/
Everyday
grepThe 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…
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!
Check out Ack (http://beyondgrep.com/why-ack/).
Oh, you were filtering for JavaScript files only. That’s as easy as
:-)
Wasn’t able to execute this through the command line:
Err find: missing argument to `-exec'https://github.com/ggreer/the_silver_searcher