Skip to content
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

Closed
CheesePizza100 opened this issue Dec 1, 2016 · 6 comments
Closed

Easy Motion 2 Char Search Not Supported #1102

CheesePizza100 opened this issue Dec 1, 2016 · 6 comments

Comments

@CheesePizza100
Copy link

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:

  • VSCode Version: 1.7.2
  • VsCodeVim Version: 4.0.4
  • OS: Windows 10 64 bit
@johnfn
Copy link
Member

johnfn commented Dec 1, 2016

Pinging @Metamist as he's the guy who worked on easymotion support. :)

@leemhenson
Copy link

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 compareKeypressSequence here https://github.com/VSCodeVim/Vim/blob/master/src/actions/actions.ts#L30 would need to be updated. At present, it looks like there's no scope for describing a match against an array, e.g. <character>[] or something.

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

@eromoe
Copy link

eromoe commented Jun 27, 2017

It show Search for 1 character: either press <Leader><Leader>w or <Leader><Leader>s. Can not search for n character with hightlight

@Chillee
Copy link
Member

Chillee commented Aug 27, 2017

@MaxfieldWalker This issue should be able to be closed now, right?

@maxfie1d
Copy link
Contributor

@Chillee Yes, this issue was resolved with PR #1967!

@Chillee
Copy link
Member

Chillee commented Aug 28, 2017

Nice!

@Chillee Chillee closed this as completed Aug 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants