5 ms·
ack and ag (the_silver_searcher) are two distinct tools. The latter automatically excludes .gitignored and binary files, just like ripgrep. In fact, it seems
by loeg 8y ago
ack and ag (the_silver_searcher) are two distinct tools. The latter automatically excludes .gitignored and binary files, just like ripgrep. In fact, it seems ag inspired ripgrep's behavior; in the blog post[0] introducing Ripgrep, BurntSushi specifically highlights that rg aims for the usability of ag:
> I will introduce a new command line search tool, ripgrep, that combines the usability of The Silver Searcher [ag] …
[0]: https://blog.burntsushi.net/ripgrep/ https://blog.burntsushi.net/ripgrep/
- sqs 8y agoThanks, did not know that!
- minusf 8y agoboth of these are slower than rg. ag has issues with big files, it's unreliable.
- zwp 8y agoI've not used ag but just a small shout out for ack: it's a single Perl file (easy to install, v1.x will work with even antique Perl), it works on weird hardware/OS (no compilation required), it contains its own man-page (ack -man) and is fast enough for typical sysadmin tasks and moderate size codebases. (Ack also supports the full PCRE syntax but that's less of an issue now rg has -P). If your work takes you to minority platforms ack is certainly worth keeping in your toolbox.
- hwj 8y agoWhat file sizes did you have issues with? I'm using ag inside my source directories and cannot remember it not doing the job.
- coldtea 8y ago>ack and ag (the_silver_searcher) are two distinct tools. The latter automatically excludes .gitignored and binary files, just like ripgrep. Only I've never been able to make ag (or pt, another similar too) respect .gitignored and other such settings as good as rg does out of the box. Plus it's slower.
- loeg 8y agoYes, I believe BurntSushi specifically highlights better .gitignore support in the (long) blog post I linked.