Write _autoenv_check_authorized_env_file to stderr

stdout might be redirected, e.g. with "cd - >/dev/null", and this
message should appear in stderr probably anyway.

I've tried to add a test for this, by redirecting stdout in .zshenv, but
cram does not handle this well (and appears to redirect stderr to stdout
anyway).

diff --git a/autoenv.zsh b/autoenv.zsh
index 95fc56a61cbd33f9a58b124b9d228f0d1d20734d..0c58f34e7ae18d7dfb6b3db1c1c2ad5425270d9c 100644 (file)
--- a/autoenv.zsh
+++ b/autoenv.zsh
@@ -222,16 +222,16 @@ _autoenv_check_authorized_env_file() {
     return 1
   fi
   if ! _autoenv_authorized_env_file $1; then
-    echo "Attempting to load unauthorized env file!"
-    command ls -l $1
-    echo ""
-    echo "**********************************************"
-    echo ""
-    cat $1
-    echo ""
-    echo "**********************************************"
-    echo ""
-    echo -n "Would you like to authorize it? (type 'yes') "
+    echo "Attempting to load unauthorized env file!" >&2
+    command ls -l $1 >&2
+    echo "" >&2
+    echo "**********************************************" >&2
+    echo "" >&2
+    cat $1 >&2
+    echo "" >&2
+    echo "**********************************************" >&2
+    echo "" >&2
+    echo -n "Would you like to authorize it? (type 'yes') " >&2
     # echo "Would you like to authorize it?"
     # echo "('yes' to allow, 'no' to not being asked again; otherwise ignore it for the shell) "