Toggle vim mode between two VSCode windows is broken
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
- Click thumbs-up 👍 on this issue if you want it!
- Click confused 😕 on this issue if not having it makes VSCodeVim unusable.
The VSCodeVim team prioritizes issues based on reaction count.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Environment:
- VSCode Version: 1.18.1
- VsCodeVim Version: 0.10.3
- OS: Linux (Ubuntu)
What happened:
When I toggle vim mode off / on in one VSCode window it somehow affects the other one. It is disables vim mode in the active windows but for the other it remains enabled (expected), however it is in somewhere in between state, neither enabled or disabled - i.e. broken.
{
"command": "toggleVim",
"key": "ctrl+k ctrl+v"
}
What did you expect to happen:
That toggleVim function will disable and enable vim mode in active window and will not affect other windows if they are.
How to reproduce it:
- Open one project in one VSCode window
- Open second project in new VSCode window (second)
- Focus first window
ctrl+shift+ptype:>Toggle vim mode, pressenter- Vim-mode should be disabled in first VSCode window
- Vim-mode broken in second VSCode window
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the toggleVim command and reproduce the behavior with two VSCode windows using the listed keybinding and steps. Trace how toggling state in the active window affects the other window. Done means each window independently enables or disables Vim mode without entering an intermediate broken state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100