From 9d668791dacd85cfd6d93f3e130367ab380d141b Mon Sep 17 00:00:00 2001
From: Gerry Agbobada <10496163+gagbo@users.noreply.github.com>
Date: Thu, 13 Jun 2019 09:03:52 +0200
Subject: [PATCH] Correct documentation of env_var file

Because of 3ed54e191bc7db1b8adf46915601f322a0d364e5 The `load-env-vars` advice is false now. Instead we can propose setting "doom-env-file" correctly, it seems to work for me.
---
 core/cli/env.el | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/core/cli/env.el b/core/cli/env.el
index c6fb2f615..714f75ba5 100644
--- a/core/cli/env.el
+++ b/core/cli/env.el
@@ -101,7 +101,8 @@ order of `doom-env-switches' determines priority."
           "#\n"
           "# It is NOT safe to edit this file. Changes will be overwritten next time\n"
           "# that `doom env refresh` is executed. Alternatively, create your own env file\n"
-          "# in your DOOMDIR and load that with `(load-env-vars FILE)`.\n"
+          "# in your DOOMDIR and load it with \n"
+          "# `(doom-load-env-vars (expand-file-name FILE doom-private-dir))`.\n"
           "#\n"
           "# To auto-regenerate this file when `doom reload` is run, use `doom env auto'\n"
           "# or set DOOMENV=1 in your shell environment/config.\n"