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

evil--jump-forward does not work #5471

Closed
eltechnic0 opened this issue Mar 12, 2016 · 8 comments
Closed

evil--jump-forward does not work #5471

eltechnic0 opened this issue Mar 12, 2016 · 8 comments
Projects

Comments

@eltechnic0
Copy link

I have tried with both the latest master and develop branch but nothing. Apparently evil-jumps-struct-idx always returns -1. I tried looking that symbol up but I am unable to find it anywhere... I am sure that the problem is there, since manually executing evil--jumps-jump-to-index does jump as expected.

@jkaye2012
Copy link

+1, any update on this?

@StreakyCobra
Copy link
Contributor

Could anyone report more information using this template? It will help us to help you :-)

@jkaye2012
Copy link

Well, in filling out the template I realized that I was not hitting leader before C-i, so this is actually not a problem for me. Apologies :)

@StreakyCobra
Copy link
Contributor

Uh? If you want to use C-i you should set dotspacemacs-distinguish-gui-tab to t in your .spacemacs.

@jkaye2012
Copy link

Do you recommend something else? Leader C-i seems to be the default binding (at least I don't believe I've changed it)

@TheBB
Copy link
Collaborator

TheBB commented May 14, 2016

I'm not sure what you're talking about. There is no SPC C-i binding.

@NathanLovato
Copy link

evil-jump-forward works here in the latest commit on the develop branch, but as explained above by @StreakyCobra, by default when you press <C-i> emacs acts as if you were pressing TAB. In your init.el file, set dotspacemacs-distinguish-gui-tab t in the dotspacemacs/init function and it should work.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Jul 20, 2020
@lebensterben lebensterben removed the stale marked as a stale issue/pr (usually by a bot) label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Forum
  
To close
Development

No branches or pull requests

6 participants