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.
This commit is contained in:
Henrik Lissner 2022-09-12 17:57:43 +02:00
parent 701f51c3d6
commit b480ed51a3
No known key found for this signature in database
GPG key ID: B60957CA074D39A3

View file

@ -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