Refactor comp-effective-async-max-jobs advice

We only need this magic in CLI sessions. It's better to only use half
the CPUs in interactive sessions (if the user has enabled
comp-deferred-compilation for some reason).

Fixes #5042
This commit is contained in:
Henrik Lissner 2021-05-12 14:50:59 -04:00
parent ce11a98b70
commit 6d2c6b44fa
3 changed files with 31 additions and 31 deletions

View file

@ -189,14 +189,7 @@ users).")
(concat local-dir-re ".*/evil-collection-vterm\\.el\\'")
(concat local-dir-re ".*/with-editor\\.el\\'")
;; https://github.com/nnicandro/emacs-jupyter/issues/297
(concat local-dir-re ".*/jupyter-channel\\.el\\'"))))
;; Default to using all cores, rather than half of them, since we compile
;; things ahead-of-time in a non-interactive session.
(defun doom--comp-use-all-cores-a ()
(if (zerop native-comp-async-jobs-number)
(setq comp-num-cpus (doom-system-cpus))
native-comp-async-jobs-number))
(advice-add #'comp-effective-async-max-jobs :override #'doom--comp-use-all-cores-a))
(concat local-dir-re ".*/jupyter-channel\\.el\\'")))))
;;