On Tue, Sep 27, 2016 at 08:43:50AM -0500, Andy Lester wrote: > > On Sep 27, 2016, at 8:12 AM, David Cantrell <[email protected]> wrote: > > OK, so there's /etc/ackrc, ~/.ackrc, and ./.ackrc. > There???s three possibility for ackrc files. > > * /etc/ackrc > * ~/.ackrc > * .ackrc in the current directory or farther up the tree > > Looking at the man page, I see that we don???t explicitly say that, and > that???s a problem. > > I???ve just opened https://github.com/petdance/ack2/issues/611 > <https://github.com/petdance/ack2/issues/611>
Actually I think that's pretty clear in the section "ACKRC LOCATION SEMANTICS". However, it's not what I was getting at. Consider a directory hierarchy like this: ~ +- foo | +- bar | +- baz +- bar +- baz I want ~/foo/bar/baz to never get searched, no matter where I am when I invoke ack - whether I'm in the home dir, or in ~/foo - but I do want to search in ~/baz when I'm in the home dir. So my idea was that when ack recurses into a directory it would look for a .ackrc file and obey it only in that directory and its sub-dirs. Something like '--ignore-dir=baz' in ~/foo/bar/.ackrc would do what I want in that case. -- David Cantrell | Minister for Arbitrary Justice -- You received this message because you are subscribed to the Google Groups "ack users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ack-users. For more options, visit https://groups.google.com/d/optout.
