VSCodeVim silently fails to initalize
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
I'm am using the latest VSCode and VSCodeVim as of 11/15/2019.
The plugin has been working fine, but after not having used VsCode for a bit and coming back, the extension no longer seems to be active. I have tried un-installing and re-installing (with restarts) with no luck. The "disable extension" setting is unchecked. The extension says its loaded and I see the doActivateExtension in the exthost log, but no vim warnings or errors in any log.
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 reproducing the inactive-extension behavior with the reported VSCode and VSCodeVim setup, then inspect the exthost log around doActivateExtension. Compare the logs with a working activation and determine whether Vim functionality returns or a diagnostic can identify the failure. No source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100