-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Helm evil scroll down / up #7123
Comments
(define-key helm-map (kbd "C-d") 'helm-next-page)
(define-key helm-map (kbd "C-u") 'helm-previous-page) |
Nice. Thank you! Don't you think this ought to be included in spacemacs's evil mode? |
It's not working in all helm buffers correctly. For example in the M-x buffer Ctrl+u seems to be for something else (while ctrl+d works). |
Yes of course, you have to unbind the existing keys that shadow these keys. That's one reason why I wouldn't want this default, to be honest. Another is that it's far more efficient to find what you want in helm by simply typing its name rather than scrolling up and down. |
Unless you don't know yet what exactly you're searching for and hence want to just scroll through a list of (functions in helm-imenu) or whatever else to get an overview or to find something you don't quite remember the name of anymore. |
If you use ivy over helm, there is a far more vimmy way to do this: https://github.com/abo-abo/hydra/wiki/hydra-ivy-replacement This gives you |
There is also a transient state for Helm on |
Is it possible to rebind |
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! |
Hello,
at first when using helm I thought you couldn't use evil/vim navigation keys at all (since it would
conflict with entering search terms),
then I discovered that you can use ctrl+j and ctrl+k.
But apparently evil style page down with ctrl+d and ctrl+u doesn't work. So I have to use the page down/page up keys, and I don't really want to since I've come to expect consistent behaviour.
The text was updated successfully, but these errors were encountered: