-
Notifications
You must be signed in to change notification settings - Fork 272
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
Enable evil-collection per mode, without global evil-want-integration disabled #115
Comments
I'm not sure how I feel about supporting the use case where you're using evil-collection but still enabling evil-want-integration/evil-integration. What about evil-collection-integration doesn't work with your config? It should be close to a 1:1 mapping with the original evil-integration file except for some naming changes. |
Specifically in my case, when I turned So from my perspective, just to enable This seems really unnecessary and not very user-friendly, since all I really want is some evil keybindings specifically when using To me it seems like evil-collection shouldn't rely at all on |
See I think if you just want elfeed, you can explicitly require that mode and call its setup function. There may or may not be some trickiness depending on how you install evil-collection.
As for that, we may want to dig deeper here. As mentioned before, evil-collection-integration should be fairly faithful to the original evil-integration, save some name changes. |
Closing for now but #60 may or may not be related/help. |
Can you provide an example of how to do this ( assuming evil-collection is installed in the normal location ) because if this is doable with a few lines this would solve my problem. Like I've said, I've had to copy elisp code directly out of evil-collection because there was no way of enabling it without also disabling This is bad because I really don't understand why you're requiring users to enable/disable unrelated features when in reality all we're doing is enabling some mode specific evil friendly keybindings. No other keybindings should change except for those in that mode, or else the user experience is really poor. Thanks for the help so far, but I don't think #60 is related to this problem. I think by fixing the original cause of this issue we'll be making evil-collection a lot more useful to people. |
evil-collection doesn't fail if you don't set
Are you sure that was the issue?
It is completely related. evil-collection is a replacement for everything in evil-integration. evil-collection does more than provide keybindings, and evil-integration absolutely does alter/make keybindings (that's the main reason
With the suggestions there implemented, you could enable "integration" for all modes and keybindings only for the ones you want to. This would mean that there wouldn't be a reason to keep |
I agree with @noctuid. If you still want to, you can suppress the warning. (I do not recommend this but it should work.)
|
Heads up if you did supress the warning, you'll want to set evil-want-keybinding to nil and evil-want-integration to t which will use evil's evil-integration.el. |
First off, thanks so much for the great collection of keybindings.
I was interested in using the evil keybindings in this package for elfeed, but after reading the documentation I noticed I had to set
evil-want-integration
tonil
. This conflicets with a bunch of existing configuration I already have set up.It seems like to only enable collections ( elfeed, in my case ), users shouldn't have to disable or enable anything. After all we're just setting some pre-defined evil-mode-map keybindings.
It would be great if I could enable some collections without disabling
evil-want-integration
.What I ended up doing was copying the evil keybindings directly and adding the to my
init.el
, which got the job done without changing anything else, but is obviously not ideal =\ .The text was updated successfully, but these errors were encountered: