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

What makes AceJump awsome in Emacs #95

Closed
favetelinguis opened this issue Nov 2, 2016 · 3 comments
Closed

What makes AceJump awsome in Emacs #95

favetelinguis opened this issue Nov 2, 2016 · 3 comments

Comments

@favetelinguis
Copy link

I have used acejump in Emacs and the three features that makes it a killer plugin there are as follows.

  1. Works over multiple windows
  2. Only searches first letter in word to make is (much) easier to navigate
  3. Matches closest are reaced using homerow keys assuming QWERTY keyboard

Are there any plans on extending Intellij version to do something like this also or are we happy with things as there are?

@favetelinguis favetelinguis changed the title Use home row as starting letters instead of ABC.. What makes AceJump awsome in Emacs Nov 2, 2016
@breandan
Copy link
Collaborator

breandan commented Nov 2, 2016

Thanks for the feedback. In theory, all three features should be possible in a future release.

  1. On the roadmap, possibly a duplicate of Multiple-editors and split-screen related issues #71, Any possibility to constrain search to start of word or camelCase? #42 (comment). PRs are highly welcome!
  2. We could flip a switch to make this available, but it would need further testing to work in all cases. The current mechanism matches one letter inside a word, but it is not guaranteed to match the first. cf. 3 beta does not find some targets for single character #79 (comment) for clarification. This would make more sense, if possible. The only downside is that fewer tags are available to use, the earlier tags are assigned. A workaround is to type the next letter in the word, ie. "wo" rather than just "w". In either case, total keystrokes should remain unchanged on average.
  3. It may be possible to use homerow keys for nearby matches. How do you define "matches closest"? By similarity to current word, by cursor distance? Is there any way we can be sure that nearby jumps are most frequent? Or is there another metric to estimate the most common jump locations based on the current cursor position? Our goal is to minimize the average time required for a jump, on average.

Thanks for using AceJump, further suggestions are highly appreciated!

@favetelinguis
Copy link
Author

favetelinguis commented Nov 3, 2016

Thank for the work on this plugin!

  1. Fantastic!
  2. Sounds like a config setting would be nice, maybe one could set a custrom regexp in config for what to match on?
  3. Intersting question, witout user data it is hard to say. My guess is that closeness to cursor is the most important since the eyes would scan this area more frequently so there is a higher chance we frequently find places we want to jump to in this area? But if we only would jump to first letter in word having 10keys on homerow would take us a long way and most often we will not get more then ~16matches wich i would say is the limit for the easiest to reach keys (homerow + e r i o w u)?

@breandan
Copy link
Collaborator

breandan commented Jul 4, 2017

Breaking this up into separate tickets.

  1. Created another ticket Support for full screen tagging #144.
  2. Partially implemented, see also Make tags user-configurable #28.
  3. Duplicates Make tags user-configurable #28.

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

2 participants