News for hackers. Stuff that matters.
Re:Feature comparison of ack, ag, git-grep, GNU grep and rip... by fragmede on Monday January 08, 2018 @10:54AM (#16097555)
At the least, I recommending moving past `find . --name '*.foo' -exec grep` pattern if you can help it.

Modern file searchers, of which `ag` is one among others, accepts `--filenametype` argument and skips the `.git` subdirectory if it exists (by default, can be toggled), so `ag --python needle` will recursively search for needle in the the current working tree in all files whos filenames end in `.py`.

Yes, you could write a function to do the same in `find`, but then you're just being stubborn. (Which is fine; my .bashrc is littered with aliases and functions of me being stubborn, but if I have to copy my .bashrc file around, I might as well install my preferred searcher to the target system if available.)

Re:Feature comparison of ack, ag, git-grep, GNU grep and rip... by xorcist on Monday January 08, 2018 @11:43AM (#16097905)
Or just use "grep". It is what it's there for.

Use --include and --exclude-dirs to do what you describe. (The latter is a good idea to set in your GREP_OPTIONS, unless you actually search .git directories.)

Re:Feature comparison of ack, ag, git-grep, GNU grep and rip... by okdana on Monday January 08, 2018 @12:21PM (#16098222)
GREP_OPTIONS is deprecated in GNU grep since i think 2.20. It will be removed in a future version, and until then it's going to print an irritating warning message every time you use it.

(I don't think there's any such plan for the various BSD greps, so if you use those exclusively you're probably fine.)

Re:Feature comparison of ack, ag, git-grep, GNU grep and rip... by petdance on Monday January 08, 2018 @12:51PM (#16098421)
Good to know. I've been considering dropping ACK_OPTIONS, and this just might put me over the edge.