$ brew uninstall ack
You don't have to choose one over the other. That's why I changed the name from "betterthangrep.com" to "beyondgrep.com". There's no need to have a ranking of "I use this over that."
An abundance of tools is good.
ack --python search-term is REALLY useful.
Beautiful. Thank you. I am stealing that for when I discuss this in other places.
Anyways, I don't really have the time for long analysis posts these days. I'm busy working on something that captures value in addition to creating it. :)
The feature I've wanted the most is the local project-specific .ackrc ability. I have some projects where I need to be able to ignore specific files/dirs; I think this feature will address that need.
That said, I don't use ack. I've tried it a few times and it looks great and works well, but honestly this particular task turns out not to be one where I demand polish and features. Really, all I want is grep.
I keep a project log file in restructured text. My entry headers look like this:
2013.03.17 Sunday, Set up base box
Use vimgrep to find all your headers:
:vimgrep /^20[0-9][0-9]/gj %
log.rst|1559 col 1| 2013.03.17 Sunday, Set up base box
log.rst|1624 col 1| 2013.03.14 Thursday, configured widgets
curl http://betterthangrep.com/ack-standalone > ~/bin/ack && chmod 0755 !#:3
In addition just changing the hostname
So, sorry I broke it, and, I can't promise that URLs are going to stay where they are unless I explicitly say that I am promising that.
I find "git grep" as fast as Ack and very flexible.
git grep is neither superset nor subset of ack. Each tool has its place.
[sorry for the plug, but it's definitely relevant to the discussion]
I count 308 perl scripts in my /usr/bin.
Python, OTOH, is always one of the first I install on every machine that doesn't have it :) pss requires no installation, no additional modules, just Python.