From 9121100bb4a619b3e95e0f427ab1fc484216c35d Mon Sep 17 00:00:00 2001 From: Henrik Lissner Date: Fri, 16 Sep 2022 17:06:23 +0200 Subject: [PATCH] fix(cli): remove redundant doom-env-file Causing the envvar file to be generated to wrong place, and thus never be updated/properly loaded at runtime. This new setting is for later, where I'll integrate the envvar generate into the profile generator proper. --- lisp/cli/env.el | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/lisp/cli/env.el b/lisp/cli/env.el index 24bf79281..1d7404345 100644 --- a/lisp/cli/env.el +++ b/lisp/cli/env.el @@ -5,13 +5,16 @@ ;; ;;; Variables -(defvar doom-env-file (doom-path doom-profile-data-dir "env") - "The location of your envvar file, generated by `doom env`. +;; (defvar doom-env-file +;; (doom-path doom-profile-dir +;; doom-profile-init-dir-name +;; "10-init-env.el") +;; "The location of your envvar file, generated by `doom env`. -This file contains environment variables scraped from your shell environment, -which is loaded at startup (if it exists). This is helpful if Emacs can't -\(easily) be launched from the correct shell session (particularly for MacOS -users).") +;; This file contains environment variables scraped from your shell environment, +;; which is loaded at startup (if it exists). This is helpful if Emacs can't +;; \(easily) be launched from the correct shell session (particularly for MacOS +;; users).") (defvar doom-env-deny '(;; Unix/shell state that shouldn't be persisted