Option to not auto-open first match

[pyrat]

Hi there,

Is it possible to configure Ack.vim so that it does not auto-open the first file which matches the search term?

Cheers,
Alastair

[mislav]

Use it like :Ack!

The bang character added to most commands will prevent the initial term to be jumped to. See #31

[pyrat]

Excellent, thanks for this tip, exactly what I needed, thanks.

On 26 January 2013 19:28, Mislav Marohnić [email protected] wrote:

Use it like :Ack!

The bang character added to most commands will prevent the initial term to
be jumped to.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-12739649.

[megalithic]

@mislav big ups for that; was driving me nuts!

[lkraav]

+2!

[shanefulmer]

Thanks - was also driving me nuts!

[pyrat]

Would be sweet if we could make this the default?

On 23 August 2013 01:30, shanefulmer [email protected] wrote:

Thanks - was also driving me nuts!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-23134033
.

[mislav]

Would be sweet if we could make this the default?

Probably won’t happen. You should make a custom command/mapping for yourself to
use the bang by default.

[pyrat]

I looked into this previously, but couldnt find a way to do it due to the
implementation of the bang. Anyone have any tips on how to achieve this?

On 23 August 2013 11:55, Mislav Marohnić [email protected] wrote:

Would be sweet if we could make this the default?

Probably won’t happen. You should make a custom command/mapping for
yourself to
use the bang by default.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-23154048
.

[ketiko]

👍 I started using ack from bash instead because of this. Awesome to know I can switch back now.

[Dieterbe]

+1 to make this configurable

[gbbr]

+1 👍 +1

[Eimis]

+1

[ejoubaud]

cabbrev Ack Ack! just made my life a whole lot easier :)

[Eimis]

@ejoubaud thanks!

[htatche]

+1

[ches]

@htatche I don't understand any further +1 on this, there are good solutions above like mappings or an abbreviation (personally I primarily use map <Leader>a :Ack! ''<Left> FWIW). Vim offers a wealth of native configurability like this that obviates the need for plugins to have a thousand settings variables.

The default behavior is not going to change, because a.) it would not be backwards-compatible and this is long-existing, and b.) it mirrors the behavior of :grep and :grep! built into Vim, which is a strong precedent and ack.vim thinly wraps it.

[SamSaffron]

The reason so many complain about this is cause Ack will always open the bottom window even if top one is in focus, that is a maddening default.

[ches]

@SamSaffron If anyone who finds it maddening would like to work up a pull request to make :Ack! behave more exactly like :grep! in that regard—populating but not opening/focusing the quickfix—I'll gladly consider it. This is a pretty small, straightforward, IMHO fairly well-factored and documented Vim plugin to hack on. I may get around to such a change myself eventually, but not in a particular hurry.

Then, people will probably complain that "I run :Ack! and it doesn't do anything!", or it creates inconsistencies with ack.vim's mappings getting applied to the results windows. I have feelings about that, but.

¯\_(ツ)_/¯

It would be largely a matter of making one function call conditional, aside from the mappings concern… Opening but not focusing the results on ! is probably a viable compromise, also a change likely to involve about three lines.

[SamSaffron]

I would love to fix this, but even :Ggrep by the demigod @tpope behaves oddly here.

If you have this configuration:

[split1]
[split2]
[quickfix results]

When you click on "quickfix result", stuff is always opened in [split2] regardless of [split1] being the window that just had focus. So my vim voodoo feeling here is that vim does not make solving this easy.

[SamSaffron]

wow ... I never know about QFEnter, this is soooo useful THANKS!

[ches]

Pardon the topical diversion for those subscribed to notifications, but I've also been made aware of vim-qf as an alternative, it may offer behavior that suits your taste and might compliment ack.vim without conflict, I haven't gotten around to trying it yet.