-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should a file type filter like --test on the CLI override a previous --notest? #321
Comments
i had thought Ack had the convention that any flag on commandline overrides Environment overrides Ackrc, (Might need a test case that fails and a 'blame" bifurcation search?) |
The |
A |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example: Go uses the convention
*_test.go
for its test files. Most of the time when searching through a codebase I'm not interested in results from test files, so I have the following in my.ackrc
:Today, I was interested in some results from test files, so I did
ack -wi root --test
, but got no results, because--notest
from my ackrc was taking effect.Is overriding
--notest
with a later--test
functionality that ack should have? If not, should--notest
and--test
issue a mutually exclusive error?The text was updated successfully, but these errors were encountered: