Tim Pope

@spolu I just tried again and `` still closes all windows with that buffer in it. I'll open a pull request

Confirmed broken after 1aa8f0cd0411c093d81f4139d151f93808e53966 and _before_ 1507e682a3d114011b732e848572e50e25cad72d (the former being a fix for an issue introduced in the latter).

`:Dispatch` captures the test output. `:Spawn` routes it directly to the terminal. These are mutually exclusive.

I'd like to see this improved, but you'll need several more checks than that: - Assignment: `x = if foo then bar else baz end` - Many (all?) operators: `x...

Doesn't surprise me, but I'm not sure what to replace it with.

I would expect an initial startup delay at worst, but regardless I'm guessing `let g:ruby_path = []` would work around it.

That sounds like maybe vim-ruby might not be the core problem.

Looks like a terminal issue. Vim-ruby might be triggering it but I have no idea how to reproduce.

One thing you could try is temporarily switching to an English locale, since that's the most obvious difference.

You can try deleting parts of `ftplugin/ruby.vim` to see if you can narrow down which part is causing the problem. My guess would be calling `s:query_path()`, just because a `system()`...