2 ms·
Interestingly enough a friend of mine kept trying to get me to use ag, since he always saw me doing relatively long "find" commands. A discussion about perfo
by aidenn0 8y ago
Interestingly enough a friend of mine kept trying to get me to use ag, since he always saw me doing relatively long "find" commands. A discussion about perfomance, ease of use, &c. later and I wrote an ag clone in shell, called "the copper searcher." Performance is similar between the two, I think I got most of the major features implemented.
Also note that if you still have UUCP infrastructure, the name "cu" will collide with an already installed program.
https://github.com/jasom/the-copper-searcher https://github.com/jasom/the-copper-searcher
- burntsushi 8y agoNeat! That's definitely better than some of the other shell clones I've seen, in that it makes an attempt to filter out files based on .gitignore. But it looks like it still gets some .gitignore stuff wrong. It's hard to handle .gitignore correctly in a simple way. In some simple tests on my Linux checkout, it is about an order of magnitude slower than ripgrep though. It looks like a good chunk of time is spent in gitignore filtering? I don't think it has multi-line search, which is something I've learned that ag users happen to love, which is why it's in the most recent release of ripgrep. :-)
- aidenn0 8y agoYeah, this was just a 1 afternoon project, and the .gitignore syntax is more complicated than I first thought.