-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easy Motion 2 Char Search Not Supported #1102
Comments
Pinging @Metamist as he's the guy who worked on easymotion support. :) |
I'd go a stage further and suggest it would be better to support n-character search instead (https://github.com/easymotion/vim-easymotion#n-character-search-motion). I took a little look at the current code and I guess the implementation of It occurs to me that "debounced-timer-based arbitrary-length keystroke collection" might be something that would be useful for other functionality, but would also complicate the existing impl a fair bit. It would be great if a maintainer could suggest whether this would be something that would be likely or unlikely to be accepted.... |
It show |
@MaxfieldWalker This issue should be able to be closed now, right? |
Nice! |
What did you do?
Was playing around with easy motion and was super excited (!!!!) for 2 character search. Since the feature is not supported it is easy to see in action.
Put the exact keys you pressed.
\+s then the first character will work as expected and matching letters will appear on the screen. the second character you enter will jump to that position on the screen.
What did you expect to happen?
The two letter sequence to be highlighted on the screen with the key sequences to jump to.
What happened instead?
Matches were shown on the screen that matched the first keypress. The second keypress caused the cursor to jump to the match it found.
Technical details:
The text was updated successfully, but these errors were encountered: