VSCodeVim / VSCodeVim/Vim

I couldn't mapping.

Open
#9,144 1 comment 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

map a <s-^>
map<silent> e <s-#>
map<silent> r <s-#>

...
And a lot of things...
But, I like your Plugin.
Could you patch these bugs please?

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 by reproducing the reported mappings in the VSCodeVim extension using the exact configuration shown in the issue, including the <s-^> and <s-#> keys. Trace how these mappings are parsed and handled, then verify that the reported mappings work without breaking other mappings; the issue does not name a file or test to start from.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.