Evil bindings are currently provided via the package kubernetes-evil. This co-exists with kubernetes-el itself (see kubernetes-evil.el) but is packaged and released entirely separately from the "main" package.
Concerns about cross-compatibility and version synchronizing aside, this is arguably an unnecessary amount of complexity for what is ultimately fairly simple functionality.
I'm proposing that we fold the Evil bindings into the main package and gate them behind a minor mode or (kubernetes-evil-activate) function.
Definition of Done
kubernetes-evil package functionality is folded into kubernetes-el itself;
User can enable/disable Evil bindings via minor mode, function, or comparable mechanism;
kubernetes-evil no longer gets released to MELPA or anywhere else;
Overview
Evil bindings are currently provided via the package
kubernetes-evil
. This co-exists withkubernetes-el
itself (seekubernetes-evil.el
) but is packaged and released entirely separately from the "main" package.Concerns about cross-compatibility and version synchronizing aside, this is arguably an unnecessary amount of complexity for what is ultimately fairly simple functionality.
I'm proposing that we fold the Evil bindings into the main package and gate them behind a minor mode or
(kubernetes-evil-activate)
function.Definition of Done
kubernetes-evil
package functionality is folded intokubernetes-el
itself;kubernetes-evil
no longer gets released to MELPA or anywhere else;