VSCodeVim / VSCodeVim/Vim

EasyMotion doesn't trigger after an action

Open
#4,624 1 comment 20 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/plugin
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Describe the bug
A common workflow for me in Vim is to combine actions with easy motion. For example:
d <leader> <leader> j to delete down some number of lines (jumping down with easy motion) or y <leader> <leader> e to yank some block of text to the right of my cursor (with the yank distance defined by easy motion). I also do with with c to change text.

To Reproduce

  1. Make sure easymotion is enabled
  2. Try d <leader> <leader> k to delete upward some number of lines
  3. Notice easymotion did not activate

Expected behavior

Environment (please complete the following information):
MacOS Mojave, most recent version of VS Code Insiders and VSCodeVim

  • VSCode version: 1.42.1582596441-insiders
  • OS: Mac OS Mojave 10.14.6

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 with EasyMotion enabled by trying d <leader> <leader> k, then compare it with a direct EasyMotion invocation and the reported y and c workflows. Read the EasyMotion and action/keybinding handling areas identified while tracing that reproduction. Done means EasyMotion activates after an action and the delete, yank, and change examples behave as described.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.