emenel/doomemacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

nit: correct comment header about startup optimizations

Browse source 
To claim they're ordered by effectiveness was silly of me, and was never
*quite* true, so I remove it altogether.
This commit is contained in:
Henrik Lissner 2022-09-15 23:47:34 +02:00
parent f34e91d3b9
commit b598d41ffb
No known key found for this signature in database
GPG key ID: B60957CA074D39A3
1 changed files with 5 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

11
lisp/doom.el
View file

@ -308,11 +308,10 @@ users).")
;;; Startup optimizations ;;; Startup optimizations
;; Here are Doom's hackiest (and least offensive) startup optimizations. They ;; Here are Doom's hackiest (and least offensive) startup optimizations. They
;; exploit implementation details and unintended side-effects, and will change ;; exploit implementation details and unintended side-effects, and will change
;; often between major Emacs releases. I've (roughly) ordered them from most to ;; often between major Emacs releases. However, I disable them if this is a
;; least effective (on Linux), and disable them if this is a daemon session ;; daemon session (where startup time matters less) or in debug-mode (to
;; (where startup time matters less) or in debug-mode (to mitigate interference ;; mitigate interference with our debugging).
;; with our debugging).
(unless (or (daemonp) init-file-debug) (unless (or (daemonp) init-file-debug)
;; PERF: `file-name-handler-alist' is consulted on each call to `require', ;; PERF: `file-name-handler-alist' is consulted on each call to `require',
;; `load', or various file/io functions (like `expand-file-name' or ;; `load', or various file/io functions (like `expand-file-name' or
@ -370,7 +369,7 @@ users).")
;; 2-3s when starting up Emacs in the terminal. Whatever slows it down at ;; 2-3s when starting up Emacs in the terminal. Whatever slows it down at
;; startup doesn't appear to affect it if it's called a little later in ;; startup doesn't appear to affect it if it's called a little later in
;; the startup process, so that's what I do. ;; the startup process, so that's what I do.
;; REVIEW: This optimization is not understood. Investigate this properly! ;; REVIEW: This optimization is not well understood. Investigate it!
(unless initial-window-system (unless initial-window-system
(advice-add #'tty-run-terminal-initialization :override #'ignore) (advice-add #'tty-run-terminal-initialization :override #'ignore)
(add-hook! 'window-setup-hook (add-hook! 'window-setup-hook