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

possilbe feature request: option to wrap ";" jump list #97

Closed
ghost opened this issue Mar 27, 2014 · 6 comments
Closed

possilbe feature request: option to wrap ";" jump list #97

ghost opened this issue Mar 27, 2014 · 6 comments

Comments

@ghost
Copy link

ghost commented Mar 27, 2014

After invoking sneak by hitting "s" and typing two letters, would hitting ";" jump to possible matches before the cursor position?

I am reluctant to overwrite s, but could part with S. Wrapping the jump list of ";" would allow for that.

@justinmk
Copy link
Owner

Probably can be tied into the solution for #88 and #95

@ghost
Copy link
Author

ghost commented Mar 28, 2014

Sounds interesting. So there would be labels, and the wrapped ; jumping functionality. Best of all all worlds. (The former, jumping bidirectionally to labels, is also present in the easy-motion plug-in, but usually there are so few matches that your ; jump motion is more intuitive.)

@justinmk
Copy link
Owner

Oh so this request is for bidirectional? Yeah there's another open issue for that. EasyMotion has ; if you set up the right <Plug> mappings. It's also getting a multi-window feature which seems useful.

@ghost
Copy link
Author

ghost commented Mar 29, 2014

Ok. I checked this out in easy-motion. There are three things to ameliorate:

  • The mapping

nmap ; ""(easymotion-next)

will also overwrite ; after a common f/F or t/T search.

  • The easymotion-next command will also jump offscreen. Instead it jump to the targets on screen in a loop.
  • After invoking two character search, you have to chose a target first. Only after this, the ""(easy-motion-next) command is valid.

There is g:EasyMotion_space_jump_first, and one could map "" to it, but this will override "" in all occasions (and problem 2. persists). As in 1., it would be nice if the mapping is active only right after a search.

@ghost
Copy link
Author

ghost commented Mar 29, 2014

That been said, after a bit of tinkering, I am happy with the following setup:

nmap (easymotion-next)
xmap (easymotion-next)
omap (easymotion-next)
nmap (easymotion-prev)
xmap (easymotion-prev)
omap (easymotion-prev)

let g:EasyMotion_space_jump_first = 1

Consider these remarks as possible feature requests. It does it job already very well.

@ghost ghost closed this as completed Mar 29, 2014
@haya14busa
Copy link
Contributor

@EPNGH FYI: easymotion/vim-easymotion#125 (comment) for problem 1.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants