-
Notifications
You must be signed in to change notification settings - Fork 43
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
[Feature Request] Match only at the beginning or end of words #211
Comments
You're thinking about having separate mappings for these "modes", or simply using Leap with this restriction? By the way, it's easy to try out. Just tweak the resulting Line 449 in 25753d8
E.g.: My experience is that it doesn't help much, on average it reduces the number of matches by ~50% or even less... and we lose the ability to jump anywhere. |
@ggandor Nice your suggestion worked thank you . I am not sure I understood the For the initial question, yes, I meant the option to replace the default behavior of leap to only match the beginning of words. I am using the lazy plugin manager and I modified the file I will continue to try this code modification as I think I usually just need to jump to beginning of words most of the time. Thank you again. |
See If you simply want to match beginnings of whitespace-separated words, there's no atom for that, like
Add those to the parenthesized OR-group, e.g., whitespace + dot:
Yep. Of course, you should do this manually after every upgrade, if you've grown to like this hack... |
Thank you very much for all of your help :) |
Thank you for this great plugin. It might be the best one I have tried for quick movements (after using easymotion, hop and flash).
To increase the likelihood that the first match is the one we would like the cursor to get at, one can consider reducing the number of matches by imposing that all matches should be at the begining ( or end) of the word.
The text was updated successfully, but these errors were encountered: