VSCodeVim / VSCodeVim/Vim

Update README section "How can I move the cursor by each display line with word wrapping?"

Open
#6,014 4 comments 2 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

As of vscode 1.52.1, vscodevim 1.18.5 this section is incorrect and leads to errors in config if copied directly.

Firstly, it seems that the format and keywords have changed, which leads to errors.

So instead of what there is, much simpler version with keywords from remap examples above this one works:

    "vim.normalModeKeyBindingsNonRecursive": [
        {
            "before": [
                "up"
            ],
            "commands": [
                "cursorUp"
            ]
        },
        {
            "before": [
                "down"
            ],
            "commands": [
                "cursorDown"
            ]
        },
        {
            "before": [
                "k"
            ],
            "commands": [
                "cursorUp"
            ]
        },
        {
            "before": [
                "j"
            ],
            "commands": [
                "cursorDown"
            ]
        }
    ]

Secondly, it says that binds such as 10j won't work, but they work correctly (at least now). Each wrapped line counts as real line during this jump.

I am not an experienced vscode or vscodevim user, so please update the documentation the way you think is right.

CC: @karlhorky #2924

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

Open the README section "How can I move the cursor by each display line with word wrapping?" and compare it with the remap examples immediately above. Update the obsolete configuration and the statement about numeric jumps so the documentation reflects the reported VS CodeVim behavior; done means the copied example uses current keywords and no longer makes incorrect claims.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.