VSCodeVim / VSCodeVim/Vim

Numbered motions resetting position after pressing number key for a second motion.

Open
#2,076 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

  • 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.


This is a BUG REPORT

  • VSCode Version: Code - Insiders 1.18.0-insider (3ffa14e5ed86b3489f86d9f8d966ae3076f94a61, 2017-10-11T05:26:57.467Z)
  • OS Version: Windows_NT x64 10.0.15063
  • Extensions:
Extension Author (truncated) Version
npm-intellisense chr 1.3.0
path-intellisense chr 1.4.2
regex chr 0.1.0
bracket-pair-colorizer Coe 0.10.9
vscode-markdownlint Dav 0.10.1
vscode-eslint dba 1.3.2
githistory don 0.2.3
python don 0.7.0
EditorConfig Edi 0.11.0
tslint eg2 1.0.11
vscode-auto-open-markdown-preview hnw 0.0.4
beautify Hoo 1.1.1
docthis joe 0.5.0
Angular2 joh 2.7.0
typescript-hero rbb 1.5.0
java red 0.11.0
autoimport ste 1.2.2
language-stylus sys 1.7.3
vscode-java-debug vsc 0.1.0
vscode-java-pack vsc 0.1.0
vim vsc 0.10.1

What happened:
brokenjumping

What did you expect to happen:
hit 3j
go down 3 lines.
hit 3j again
be 6 lines from where I started.
How to reproduce it:
What's odd is that this only happens in some files. I've not been able to pin down the triggering effect.

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

No source file or test is named. Start by reproducing 3j twice in files where the problem occurs, then narrow down what distinguishes those files and trace the numbered-motion handling. Done means that repeated motions continue from the current position and the behavior is covered by a regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.