-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opens File in unexpected split #205
Comments
To understand what you're asking or wishing to behave differently, please try doing the same thing with If you want to have more control over where results/splits are opened, take a look at #170 and see if it achieves what you wish for. vim-qf is another alternative. As far as behaving like netrw, you're probably just going to want to seek another plugin if that's what you'd prefer. Again, ack.vim is designed to be seamlessly familiar to a user of |
I am observing the same issue. From the result panel at the bottom:
|
Hi there Really sorry for leaving you waiting for so long. Totaly forgotten. Just stumbled over it on google again.
So after all I think Muffos issue should be a own issue and this should be closed as obviously bad Issue. To explain what i meant and to at least learn something about vimgrep i would be thankfully if you explain me the following. I have a fresh vim instance with one split.
The cursor is in Split If I use If I use I have no idea why it used the secondlast split.
And the curso is in split So if anybody could explain that to me i would be really thankfull. |
Thanks for the clarification! |
I am experiencing this too. |
It seems like a file is open in the first opened split. This is quite irritating. Am I doing something wrong, or is this a limitation of ack.vim ? It would be great to open the file in the last active split. And even better (at least for me) would be if ack woul behave like vinegar.vim/newtr and instead of open a quickfixlist, showing the result in the active split, and open the file there.
The text was updated successfully, but these errors were encountered: