eb9fa90adf
Parinfer uses `evil-define-key' without loading evil. This means that if evil is installed *after* parinfer, parinfer will throw up void-function errors, because evil-define-key (a macro) wasn't expanded at compile-time. So we make extra sure evil is installed before parinfer (or at least, make sure evil-define-key is autoloaded at install time, in case evil was installed in another session).
15 lines
570 B
EmacsLisp
15 lines
570 B
EmacsLisp
;; -*- no-byte-compile: t; -*-
|
|
;;; editor/parinfer/packages.el
|
|
|
|
(when (featurep! :feature evil)
|
|
;; Parinfer uses `evil-define-key' without loading evil, so if evil is
|
|
;; installed *after* parinfer, parinfer will throw up void-function errors.
|
|
;; because evil-define-key (a macro) wasn't expanded at compile-time. So we
|
|
;; make sure evil is installed before parinfer...
|
|
(package! evil)
|
|
;; ...and that it can see `evil-define-key' if evil was installed in a
|
|
;; separate session:
|
|
(autoload 'evil-define-key "evil-core" nil nil 'macro))
|
|
|
|
(package! parinfer)
|