Andy Lester

We need to tread carefully here. There have been problems and surprised expectations surrounding everything related to ack's handling of filter mode, STDIN detection, etc since the dawn of time,...

Seems to me that perhaps the core problem here is that ack doesn't throw a warning if it's sent data on STDIN and called with `-f`. I can't see why...

We already tell people "Hey, you're using -l and -A together, and that doesn't make sense." I think it would also make sense to say "Hey, you're using -f or...

ack's `-f` only finds files. ack is only interested in files, not directories. It is not meant to be a general-purpose finder of things.

I'm not following. What exactly is it you're wanting ack to do?

Please note that you don't need the `!` delimiters when specifying the pattern.

So if I'm understanding correctly, given this setup: $ mkdir -p foo storage/project_{1,2}/{foo,config} $ find . -type f $ find . -type d . ./storage ./storage/project_2 ./storage/project_2/config ./storage/project_2/foo ./storage/project_1 ./storage/project_1/config...

I'm open to suggestions on how this feature would work without breaking existing usage. I'm talking about discussion of how the feature would work, not actual code yet.

So let's talk this out in specifics. You have the tree you showed above: ``` foo/ storage/ project_1/ foo/ ... config/ ... project_2 foo/ ... config/ ... ... ``` So...

> I'm not sure why this needs to be so complicated. I hope it's not, but past experience has shown that what seems simple is rarely so. Matching `--ignore-path` vs....