Doc: why ag.vim vs ack.vim

[ku1ik]

Hi,

I just noticed this project and I wondered if there's really a need for the fork. To make ack.vim work with ag is just a matter of:

let g:ackprg = 'ag --nogroup --nocolor --column'

I use ag with ack.vim like that and it just works.

No hard feelings :)

[rking]

That does work, but:

• I use a shared config wherever I have a $HOME. So when I happen to not-have af, I can fall back to :Ack
• :Ag is 25% shorter than :Ack. =)
• At this point, IMO the implementation is better for ag.vim, since it uses autoload. I should pull req ack.vim now that I've worked out the (tiny) hitches with this.

[rking]

Oh, I forgot the most significant factor in the decision to fork.

Because ack actually has several features ag doesn't, and probably won't (like searching by filetype).

I'll leave this issue open as a doc task.

[ku1ik]

Fair enough :)

[schickling]

Correct me if I'm wrong but ag has filetype filtering by now, doesn't it?

[losingkeys]

What do you mean by filetype filtering?

[schickling]

For example searching just for html files by: ag div --html

[losingkeys]

Ohh, you can always do :Ag --html search dir, but I don't thing there's a special command like :AgFile (searches for files with ag -g)

On Jan 10, 2014, at 5:05 PM, Johannes Schickling [email protected] wrote:

For example searching just for html files by: ag div --html

— Reply to this email directly or view it on GitHub.

[CarlosMorfin]

When I execute the command: Ack '=' the following line appears: 1 || /bin/bash/: ag: command not fount

In .vimrc I have set Ag behind the scene: let g:ackprg = 'ag --nogroup --nocolor --column'

Can someone tell me how to fix this please