junegunn / junegunn/vader.vim

Vader-workbench tab stays open after test execution on Windows

Open
#39 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Vim Script
Stars
599
Forks
40
PR merge metrics
No merged PRs in 30d

Description

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).

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue with Vader and the stripped-down Vim setup described, using Vim 7.4 on Windows and the referenced endoscope tests. Compare the Windows and Ubuntu behavior when quitting the Vader results tab; done means the unexpected workbench tab no longer remains open after test execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
testing-qa, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.