From 0381c7868eed5b5139f523c2aa76a93e31a3c51e Mon Sep 17 00:00:00 2001 From: Henrik Lissner Date: Fri, 1 Oct 2021 18:12:34 +0200 Subject: [PATCH] fix: doom/reload not restoring initial envvars 'doom/reload' should and cannot regenerate the user's envvar file, because it's not typically running in your shell, but it should reload your existing envvar file. Fix #5399 Ref #5344 --- core/autoload/config.el | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/core/autoload/config.el b/core/autoload/config.el index 6a1e15bf9..de34727ad 100644 --- a/core/autoload/config.el +++ b/core/autoload/config.el @@ -76,9 +76,8 @@ package list, and lastly, reloads your private config.el. Runs `doom-after-reload-hook' afterwards." (interactive) (mapc #'require (cdr doom-incremental-packages)) - (doom--if-compile (format "%S sync" doom-bin) - (let ((doom-reloading-p t) - doom-env-file) + (doom--if-compile (format "%S sync -e" doom-bin) + (let ((doom-reloading-p t)) (doom-run-hooks 'doom-before-reload-hook) (doom-initialize 'force) (with-demoted-errors "PRIVATE CONFIG ERROR: %s"