From b480ed51a30a0d8184bcadb40923ca76f04aeebd Mon Sep 17 00:00:00 2001 From: Henrik Lissner Date: Mon, 12 Sep 2022 17:57:43 +0200 Subject: [PATCH] refactor(lib): suppress map! at compile/batch time It's not useful in those scenarios, and is more likely to throw up unrecoverably keybind conflict errors, when load order is determined by an over-eager byte-compiler, rather than Doom's standard startup process. --- lisp/doom-keybinds.el | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lisp/doom-keybinds.el b/lisp/doom-keybinds.el index 1550e6ba9..09ab0090b 100644 --- a/lisp/doom-keybinds.el +++ b/lisp/doom-keybinds.el @@ -456,7 +456,9 @@ States Don't (map! :n :leader :desc \"Description\" \"C-c\" #'dosomething) (map! :leader :n :desc \"Description\" \"C-c\" #'dosomething)" - (doom--map-process rest)) + (when (or (bound-and-true-p byte-compile-current-file) + (not noninteractive)) + (doom--map-process rest))) (provide 'doom-keybinds) ;;; doom-keybinds.el ends here