Easymotion with operator
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Feature Request
What happened:
easymotion motions cannot be composed with edit commands.
What did you expect to happen:
If I enter an edit command and then perform a cursor move via easymotion, the edit command should be applied to the range of text covered by the cursor move just as it does for other motion commands such as f, t, and w.
Environment:
- Extension Name: vim
- Extension Version: 0.10.9
- OS Version: Windows_NT x64 6.1.7601
- VSCode version: 1.19.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how edit commands compose with the existing f, t, and w motion handlers, then compare that path with easymotion handling. Done means an edit command followed by an easymotion cursor move applies to the range covered by that move, matching the behavior of the other motions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100