-
Notifications
You must be signed in to change notification settings - Fork 265
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
Consistency: helm, ivy #25
Comments
Hmnn, which keys do you think are inconsistent? I'm a little wary here because:
If we're trying to make it consistent, Helm is the one that needs to 'give way'. |
I'm thinking the motion key in the Ivy minibuffer, etc. For now Ivy only has ivy-occur bindings. I do not know Ivy very well and it seems that you do not know Helm very well, so I guess we have some homework to do! :) No problem with making Helm "give way" :) |
I used helm for a while until I settled on ivy and it definitely has a few different conventions to it. Ivy as a package is a lot more 'emacs'-like. I'm not sure the ivy minibuffer needs evil keys (maybe it's just because I myself never use motion-related keys in the minibuffer). |
I suppose this would only make sense for people who use evil-minibuffer (like me! :p). Let's keep this open for anyone to contribute. Otherwise I'll take a look at it when I have time. |
I've overhauled helm: most (all?) issues are fixed, many Evil classic are added, and it just happens that it matches Ivy bindings quite well. There is still a lot of work to do, but that'll come with time. |
I guess it would make sense for those bindings to be consistent.
Spacemacs has done some work in the area.
The text was updated successfully, but these errors were encountered: