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!
![CSS 3D Folding Animation]()
Google Plus provides loads of inspiration for front-end developers, especially when it comes to the CSS and JavaScript wonders they create. Last year I duplicated their incredible PhotoStack effect with both MooTools and pure CSS; this time I'm going to duplicate...
![Regular Expressions for the Rest of Us]()
Sooner or later you'll run across a regular expression. With their cryptic syntax, confusing documentation and massive learning curve, most developers settle for copying and pasting them from StackOverflow and hoping they work. But what if you could decode regular expressions and harness their power? In...
![Cross Browser CSS Box Shadows]()
Box shadows have been used on the web for quite a while, but they weren't created with CSS -- we needed to utilize some Photoshop game to create them. For someone with no design talent, a.k.a me, the need to use Photoshop sucked. Just because we...
![Vertically Centering with Flexbox]()
Vertically centering sibling child contents is a task we've long needed on the web but has always seemed way more difficult than it should be. We initially used tables to accomplish the task, then moved on to CSS and JavaScript tricks because table layout was horribly...
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