Don't load core-cli on doom/reload
Hopefully addresses "Device 1 is not a termcap terminal device" errors, due to core-cli changing `debugger`. core-cli should never be loaded in an interactive session anyway. Possibly fixes #4849
This commit is contained in:
parent
d79cea2e4c
commit
f523830a0e
1 changed files with 0 additions and 1 deletions
|
@ -74,7 +74,6 @@ package list, and lastly, reloads your private config.el.
|
||||||
|
|
||||||
Runs `doom-after-reload-hook' afterwards."
|
Runs `doom-after-reload-hook' afterwards."
|
||||||
(interactive)
|
(interactive)
|
||||||
(require 'core-cli)
|
|
||||||
(when (and IS-WINDOWS (file-exists-p doom-env-file))
|
(when (and IS-WINDOWS (file-exists-p doom-env-file))
|
||||||
(message "Can't regenerate envvar file from within Emacs. Run 'doom env' from the console"))
|
(message "Can't regenerate envvar file from within Emacs. Run 'doom env' from the console"))
|
||||||
;; In case doom/reload is run before incrementally loaded packages are loaded,
|
;; In case doom/reload is run before incrementally loaded packages are loaded,
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue