Closed dionyziz closed 10 years ago
That's something that you'll probably want to put in a project-level .ackrc file. For instance, at work I have:
# Known cruft
--ignore-file=ext:log
--ignore-file=ext:pdf
--ignore-file=ext:dat
--ignore-file=is:Tags
You could also use the --known-types
flag that only checks for files of types that ack can identify. This was the behavior of ack 1.x.
Why ack did not ignore TAGS file by default? Documentation says that ack it is grep for programmers and as I understood it's mean that ack has good default setting for developers?
I decided against it because it's entirely likely that folks could have a "tags" file somewhere in their tree that is not related to ctags
. Putting it in your project's .ackrc
works fine.
Sorry, i think about uppercase TAGS file, but after some thinking I undestood that it will not work on MS Windows systems.
Ctag files in the project root (a file called tags) is searched when using ack. Is this desired behavior? Usually when searching in source code we're not interested in this.