Josh Hoff

Note: #99 introduces some code that has the same problem as this issue, so it needs to be checked too.

Strange. I guess it could be an ag issue too... But I've never seen ag mix the paths like this before. Maybe someone can make a small reproducible vim script...

Also don't open the error/location list when there aren't any matches because of an error (any nonzero exit status?)

It [seems like](http://stackoverflow.com/a/9828589/) checking `v:shell_error` would work, but that doesn't seem to be set for `:grep`. The error message could be parsed, but sometimes (imo) it's confusing. For instance, if...

`:Ag` opens the [quickfix window](http://vimdoc.sourceforge.net/htmldoc/quickfix.html#quickfix-window) (`:LAg` opens the [location list](http://vimdoc.sourceforge.net/htmldoc/quickfix.html#location-list-window)). These might open in strange spots depending on what you (or other plugins) have set ['splitbelow'](http://vimdoc.sourceforge.net/htmldoc/options.html#'splitbelow') or ['splitright'](http://vimdoc.sourceforge.net/htmldoc/options.html#'splitright') to.

Hmm... ag.vim uses [`:grep`](http://vimdoc.sourceforge.net/htmldoc/quickfix.html#:grep) internally. Do you mind doing some tests using `:grep` (you might need to do `:copen` manually after searching) with split windows and see if you get...

That makes sense. You could use :Ag! Too avoid jumping to matches right after searching, then one if the mappings (see :h ag) as a workaround. Other than that we...

Hmm, what if you tried adding: ``` viml let g:ag_qhandler="copen" let g:ag_lhandler="lopen" ``` to your vimrc? I can't recall why these variables were created, but I think they've been there...

@typeoneerror Mind opening an issue for this option? I thought about it before... but it seemed like it was going against vim's convention, but if people will use it I'm...

@exchgr is this no longer an issue then? Sorry for the delay, I'm just now going through the issues again. A quick scan of this one looks like you have...