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

A separate jump list for vim-like tag navigation #4

Open
igoralmeida opened this issue May 24, 2020 · 0 comments
Open

A separate jump list for vim-like tag navigation #4

igoralmeida opened this issue May 24, 2020 · 0 comments

Comments

@igoralmeida
Copy link

Hi, thanks for better-jumper!

It seems doom emacs uses better-jumper instead of some evil jumping functions, so here's a [long] question. As a vim user, I am missing the separate "tag stack" functionality when using emacs, and I was wondering if better-jumper could work for that.

Basically, the jump list is polluted by several commands (for example, evil-window-top, evil-forward-section-begin, evil-scroll-down...) that are inconsequential to code navigation, and it would be nice to jump backward and forward only to places where there are definitions of functions, for example. Those intermediate jumps -- in, for example, the current file -- can be distracting when trying to go back to the last function definition. Of course, there are cases where they are valuable.

I took a look at better-jumper.el and wondered if there could be a better-jumper-set-definition-jump (like better-jumper-set-jump) the uses a separate jump list struct. This would probably need to be similar to the 'window context since you'd be navigating to different files with something like evil-goto-definition.
I don't fully understand the code, but it seems that the calls to better-jumper--get-struct and better-jumper--push could have some more args to be able to differentiate between this "better-jumper-set-definition-jump" proposal and better-jumper-set-jump, to make sure the correct jump list is used.

Thoughts?

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

1 participant