VSCodeVim / VSCodeVim/Vim

Suddenly lost all VIM functionality

Open
#8,806 0 comments 0 reactions 0 assignees View on GitHub

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 not sure there is a bug, but: I've used Vim for 25 years, VSCode with the vscodevim extension for 5 years, and haven't touched any configurations/settings for months.

In December all was as it should be. I took a couple weeks for the holidays, just opened VSCode for the first time again today - and no Vim bindings work. No changes in anything except whatever automatic updates happened in the last couple of weeks.

I've rebooted multiple times, enabled/disabled the Vim extension, opened very different repositories (Text, JavaScript, Python, etc) - no Vim!

To Reproduce
Steps to reproduce the behavior:

Open any existing text file

Use mouse to select any position in the file.

Press the "Esc" key on keyboard.

Press "o" key.

Expected behavior
New empty line below cursor position, ready to accept keyboard input.

Actual Behavior

The character "o" is entered at the cursor insertion point.

Environment:

  • Extension (VsCodeVim) version: v1.27.2
  • VSCode version: : 1.85.1
  • OS: Windows 11 Pro

Additional context

I've installed & configured multiple VSCode extensions over many years. I assume my problem is from a configuration conflict rather than an actual bug in the vscodevim extension, but I have no idea where. Totally re-installing & reconfiguring VSCode from scratch would be a 2-3 week full time nightmare - I'd be very appreciative of any ideas how to avoid that.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported VSCode 1.85.1 and VsCodeVim v1.27.2 environment, then inspect enabled extensions and keybinding or configuration conflicts while following the listed Esc/o reproduction steps. Done means Vim normal-mode behavior is restored without requiring a full VSCode reinstallation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vim, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.