doom refresh -> doom sync

refresh isn't going anywhere, but sync will be the canonical command
here on out, because it is more appropriate for kind of work it will be
doing in the future.
This commit is contained in:
Henrik Lissner 2020-02-19 23:34:16 -05:00
parent f29d5ed034
commit 8a7763337d
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
9 changed files with 16 additions and 16 deletions

View file

@ -68,16 +68,16 @@ And jumps to your `doom!' block."
(defun doom/reload ()
"Reloads your private config.
This is experimental! It will try to do as `bin/doom refresh' does, but from
within this Emacs session. i.e. it reload autoloads files (if necessary),
reloads your package list, and lastly, reloads your private config.el.
This is experimental! It will try to do as `bin/doom sync' does, but from within
this Emacs session. i.e. it reload autoloads files (if necessary), reloads your
package list, and lastly, reloads your private config.el.
Runs `doom-reload-hook' afterwards."
(interactive)
(require 'core-cli)
(when (and IS-WINDOWS (file-exists-p doom-env-file))
(warn "Can't regenerate envvar file from within Emacs. Run 'doom env' from the console"))
(doom--compile (format "%s refresh -e" doom-bin)
(doom--compile (format "%s sync -e" doom-bin)
:on-success
(let ((doom-reloading-p t))
(doom-initialize 'force)
@ -99,7 +99,7 @@ This is much faster and safer than `doom/reload', but not as comprehensive. This
reloads your package and module visibility, but does not install new packages or
remove orphaned ones. It also doesn't reload your private config.
It is useful to only pull in changes performed by 'doom refresh' on the command
It is useful to only pull in changes performed by 'doom sync' on the command
line."
(interactive)
(require 'core-cli)