I'm not that happy with having the evil integration functionality as a part of key-leap.el. In order for it to work, evil must have been required before the function is called. It would be better if the integration occured in its own package that properly specifies its dependency on key-leap and evil. This would mean key-leap.el is freed of the evil integration, which did not really belong there in the first place.
The solution would be to create a new package in this repository, evil-key-leap.el that does the same thing that key-leap-create-evil-motion is currently doing.
It would require the following steps:
- Change the melpa recipe to explicitly use only key-leap.el as the package source
- Create
evil-key-leap.el and put the integration code there. Its package header should specify key-leap and evil as dependencies
- Remove the implementation of
key-leap-create-evil-motion and mark it as obsolete
I'm not that happy with having the evil integration functionality as a part of key-leap.el. In order for it to work, evil must have been required before the function is called. It would be better if the integration occured in its own package that properly specifies its dependency on key-leap and evil. This would mean key-leap.el is freed of the evil integration, which did not really belong there in the first place.
The solution would be to create a new package in this repository,
evil-key-leap.elthat does the same thing thatkey-leap-create-evil-motionis currently doing.It would require the following steps:
evil-key-leap.eland put the integration code there. Its package header should specify key-leap and evil as dependencieskey-leap-create-evil-motionand mark it as obsolete