gitback/doomemacs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0ec4d6ee43
doomemacs/modules/config/literate/init.el

40 lines
1.4 KiB
EmacsLisp
Raw Normal View History

config/literate: earlier check & no byte-compile Making the compile check happen earlier fixes an edge case where the resulting files from a literate config being tangled into multiple files aren't recognized by Doom's package management or autoload generation systems. Disabling byte-compiling fixes an all too common issue where packages and macros are undefined at compile time, causing a plethora of invalid function errors. Leave byte-compilation to `bin/doom compile`!
2018-06-08 22:23:13 +08:00
;;; config/literate/init.el -*- lexical-binding: t; -*-
Add :config literate module It will tangle and byte-compile a config.org in your private config. Doom will then load the resulting config.elc later. Org is only loaded when updating this file.
2018-06-05 21:38:58 +08:00
;;; config/literate/config.el -*- lexical-binding: t; -*-
compile/literate: refactor & recompile on save And add autoloaded commands. This may need work to ensure you don't spawn multiple instances of Emacs all vying to compile the same file.
2018-06-05 22:09:03 +08:00
(defvar +literate-config-file
(expand-file-name "config.org" doom-private-dir)
"The file path of your literate config file.")
Add :config literate module It will tangle and byte-compile a config.org in your private config. Doom will then load the resulting config.elc later. Org is only loaded when updating this file.
2018-06-05 21:38:58 +08:00
compile/literate: refactor & recompile on save And add autoloaded commands. This may need work to ensure you don't spawn multiple instances of Emacs all vying to compile the same file.
2018-06-05 22:09:03 +08:00
(defvar +literate-config-dest-file
(expand-file-name "config.el" doom-private-dir)
"The file path that `+literate-config-file' will be tangled to, then
byte-compiled from.")
Add :config literate module It will tangle and byte-compile a config.org in your private config. Doom will then load the resulting config.elc later. Org is only loaded when updating this file.
2018-06-05 21:38:58 +08:00
;;
compile/literate: refactor & recompile on save And add autoloaded commands. This may need work to ensure you don't spawn multiple instances of Emacs all vying to compile the same file.
2018-06-05 22:09:03 +08:00
(defun +literate-compile (&optional load)
"Tangles & compiles `+literate-config-file' if it has changed. If LOAD is
non-nil, load it too!"
(let ((org +literate-config-file)
config/literate: earlier check & no byte-compile Making the compile check happen earlier fixes an edge case where the resulting files from a literate config being tangled into multiple files aren't recognized by Doom's package management or autoload generation systems. Disabling byte-compiling fixes an all too common issue where packages and macros are undefined at compile time, causing a plethora of invalid function errors. Leave byte-compilation to `bin/doom compile`!
2018-06-08 22:23:13 +08:00
(el +literate-config-dest-file))
(when (file-newer-than-file-p org el)
config/literate: log compilation
2018-06-05 22:14:38 +08:00
(message "Compiling your literate config...")
config/literate: earlier check & no byte-compile Making the compile check happen earlier fixes an edge case where the resulting files from a literate config being tangled into multiple files aren't recognized by Doom's package management or autoload generation systems. Disabling byte-compiling fixes an all too common issue where packages and macros are undefined at compile time, causing a plethora of invalid function errors. Leave byte-compilation to `bin/doom compile`!
2018-06-08 22:23:13 +08:00
;; We tangle in a separate, blank process because loading it here would
;; load all of :lang org (very expensive!). We only need ob-tangle.
compile/literate: refactor & recompile on save And add autoloaded commands. This may need work to ensure you don't spawn multiple instances of Emacs all vying to compile the same file.
2018-06-05 22:09:03 +08:00
(or (zerop (call-process
"emacs" nil nil nil
"-q" "--batch" "-l" "ob-tangle" "--eval"
(format "(org-babel-tangle-file \"%s\" \"%s\" \"emacs-lisp\")"
config/literate: earlier check & no byte-compile Making the compile check happen earlier fixes an edge case where the resulting files from a literate config being tangled into multiple files aren't recognized by Doom's package management or autoload generation systems. Disabling byte-compiling fixes an all too common issue where packages and macros are undefined at compile time, causing a plethora of invalid function errors. Leave byte-compilation to `bin/doom compile`!
2018-06-08 22:23:13 +08:00
org el)))
(warn "There was a problem tangling your literate config!"))
config/literate: log compilation
2018-06-05 22:14:38 +08:00
(message "Done!"))))
Add :config literate module It will tangle and byte-compile a config.org in your private config. Doom will then load the resulting config.elc later. Org is only loaded when updating this file.
2018-06-05 21:38:58 +08:00
compile/literate: refactor & recompile on save And add autoloaded commands. This may need work to ensure you don't spawn multiple instances of Emacs all vying to compile the same file.
2018-06-05 22:09:03 +08:00
;; Let 'er rip!
(+literate-compile)
Add :config literate module It will tangle and byte-compile a config.org in your private config. Doom will then load the resulting config.elc later. Org is only loaded when updating this file.
2018-06-05 21:38:58 +08:00
;; No need to load the resulting file. Doom will do this for us after all
;; modules have finished loading.
Reference in New Issue Copy Permalink