search

junegunn / vader.vim

A simple Vimscript test framework
589 stars 40 forks source link

Vader-workbench tab stays open after test execution on Windows #39

Open idbrii opened 9 years ago

idbrii commented 9 years ago

Using vader ad7f1b70ebcf76de86d1991732146f2ebabe3ba4. I updated from 2626295f48f6eab3b351e9443125dae6cbdbdcd5 and it occurred then too.

When I run tests, the workbench tab stays open even after using q to quit the Vader results tab. It seems to be a tab that you'd never expect me to see. I don't see any error in :messages

This only happens on Windows. Using the same vim setup on Ubuntu, I didn't see this problem.

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 10 2013 14:38:33) MS-Windows 32-bit GUI version with OLE support Compiled by mool@tororo (from vim.org)

Windows 7 SP1.

I also tried with a stripped down vim setup using tpope/pathogen, tpope/sensible, vader, and idbrii/endoscope (which has the tests).

junegunn commented 9 years ago

So it's not reproducible on GVim or terminal Vim on Ubuntu, but only on Windows GVim?

blueyed commented 9 years ago

@idbrii Would be great if you could git-bisect this to a particular commit.

idbrii commented 9 years ago

It's from when workbench tab was first added: 176371f6c838eebca08d5ea8a23f32ed759c068e

Test:

#! /bin/bash
gvim -N -U NONE -u test_vimrc +Vader ../endoscope/test/mixed.vader

test_vimrc

filetype off
set rtp=~/.vim/bundle/vader,$VIMRUNTIME
filetype plugin indent on