VSCodeVim / VSCodeVim/Vim

In insert mode, hitting `<Down>` after `<C-Left>` does not take current position into account

Open
#1,664 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/motion 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): Bug report

Environment:

  • VSCode Version: 1.11.2
  • VsCodeVim Version: 0.7.0
  • OS: Arch Linux
  1. Open a python file
  2. Write the following in it:
tuples = (
	(1, 12345),
	(1, 67890),
)

Move the cursor to be right after 5 in the first 12345. If you now press Ctrl + followed by , the cursor will end up right after 0 instead of right before 6, where you would expect it to be (and where it would be by hitting arrow left 5 times instead of previous word).

This works both in and out of insert mode. I'm not sure if this is a vim or native vscode issue admittedly.

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 behavior in a Python file using the example and the Ctrl-Left followed by Down sequence, both in and out of insert mode. First determine whether the cursor handling belongs to VSCodeVim or native VS Code; done means Down accounts for the current position and places the cursor before 6, matching repeated left-arrow behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.