Andy Lester
Andy Lester
If I search for something like ack foo --range-end=marker filename with a `--range-end` without a `--range-start`, then once ack hits that range end, there's no point in scanning the rest...
t/ack-x.t fails with File /tmp/ABV34l3UWo is still readable despite our attempts to changes its permissions at t/ack-x.t line 79.
From #233 from @rkta Maybe you could add cscope's cscope.out (not sure if you could detect the file type independent from the name)? Using ack with vim's quickfix list it...
We've had to SKIP tests in two tests under Travis because Travis can't find `stty` in its path. Solve this problem.
The grep docs say: The grep utility exits with one of the following values: 0 One or more lines were selected. 1 No lines were selected. >1 An error occurred....
If I do `some_command | ack foo -p`, the same proximity rules should still apply, even though the line numbers aren't showing up.
I'm running the new 2.0 on a big code repo, and I think it is dragging on certain files that 1.x skipped. I'm wondering what they would be. What if...
Currently our `--ignore-file`s are: ``` $ ack --dump | ack ignore-file --ignore-file=ext:bak --ignore-file=ext:gif,jpg,jpeg,png --ignore-file=ext:gz,tar,tgz,zip --ignore-file=ext:pdf --ignore-file=is:.git --ignore-file=match:/[.-]min[.]js$/ --ignore-file=match:/[.]css[.]map$/ --ignore-file=match:/[.]css[.]min$/ --ignore-file=match:/[.]js[.]map$/ --ignore-file=match:/[.]js[.]min$/ --ignore-file=match:/[.]min[.]css$/ --ignore-file=match:/[._].*\.swp$/ --ignore-file=match:/^#.+#$/ --ignore-file=match:/core\.\d+$/ --ignore-file=match:/~$/ --ignore-file=is:ack-standalone --ignore-file=is:tags ``` See...
`--ignore-dir=foo` takes a regex, not a glob. `--ignore-dir=abc*` will ignore directory `ab` as well as `abc` and `abcccccc`. This is not what someone would expect if they thought that was...
See https://stackoverflow.com/questions/43685368/ignore-egg-info-directories-with-ack-grep/43702798