VSCodeVim / VSCodeVim/Vim

Shortcuts displayed in Command Pallete are not correct with VSCodeVIM

Open
#1,864 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

kind/enhancement
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):

Environment:

  • VSCode Version: 1.13.1
  • VsCodeVim Version: 0.8.6
  • OS: Ubuntu 16.04 LTS

What happened:
In Command Pallete (after pressing Ctrl+Shift+P) displayed keyboard shortcuts tips are standard one, not this which really work.

What did you expect to happen:
If e.g. shortcut Ctrl+W is overwritten by VSCodeVim (and now you must use :tabc), I expect that when I search Close Windows in Command Pallete I see :tabc shortcut tip, not Ctrl+W. This apply of course for every shortcut which is different.

How to reproduce it:
Press Ctrl+Shift+P, type close window and see that provided shortcut tip is Ctrl+W, even when Ctrl+W doesn't work.

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

Reproduce the issue in the VS Code Command Palette by pressing Ctrl+Shift+P and searching for “close window” with the reported VSCodeVim behavior. Trace how VSCodeVim overrides Ctrl+W and how the Command Palette displays shortcut tips. Done means overridden commands show their effective VSCodeVim shortcut instead of Ctrl+W.

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
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.