From 3da2f3702e23574b9f06f7410ae45e1fa826f652 Mon Sep 17 00:00:00 2001 From: syl20bnr Date: Sun, 12 Feb 2017 22:59:26 -0500 Subject: [PATCH] emacs-lisp: don't use custom-set-variables As it make evil to error when the delq form is written the customize file, instead we call the set method manually and it works fine. Would be better and more future proof to curry the set function into a named function of 0 arity for evil-intercept-maps custom setting. --- layers/+lang/emacs-lisp/packages.el | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/layers/+lang/emacs-lisp/packages.el b/layers/+lang/emacs-lisp/packages.el index 47f9ef74a..cef7a3e5c 100644 --- a/layers/+lang/emacs-lisp/packages.el +++ b/layers/+lang/emacs-lisp/packages.el @@ -75,10 +75,13 @@ "dF" 'spacemacs/edebug-instrument-defun-off)) ;; since we evilify `edebug-mode-map' we don't need to intercept it to ;; make it work with evil - (custom-set-variables - '(evil-intercept-maps - (delq (assq 'edebug-mode-map evil-intercept-maps) - evil-intercept-maps))) + (evil-set-custom-state-maps + 'evil-intercept-maps + 'evil-pending-intercept-maps + 'intercept-state + 'evil-make-intercept-map + (delq (assq 'edebug-mode-map evil-intercept-maps) + evil-intercept-maps)) (evilified-state-evilify-map edebug-mode-map :eval-after-load edebug :bindings