= 27d567bc2d48d9f40e9ccc20ea370b15)
AngryParsley comments on What are you working on? February 2013 - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (59)
This is a follow up to the last time I posted in a WAYWO thread.
A little over a year ago, I started working on a code searching tool in my spare time. It's been more successful than I ever thought it would be. The GitHub repo has more watchers than Ack, the project I set out to imitate. I learned a lot about optimizing, profiling, benchmarking, and using pthreads.
It's also had a nice side-benefit: random people online recognize me.
I frequently have cause to grep -r our entire codebase, so I think I'll be having a play with this. Thank you!
Edit: And you've helped me impress my boss. Well done :-D (We use Ubuntu 10.04 VMs as servers, so the Lucid deb was just the thing.) HEY EVERYONE: If you ever find yourself having to grep -r a codebase, just use ag instead.
Feature request: output in the same format as grep -r (to feed to other scripts). Edit: and lo, it does this automatically when its output is a pipe. Win!