Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

[PATCH][doc] BASHENV -> BASH_ENV typo

X-seq: zsh-workers 52685
From: Stephane Chazelas <stephane@xxxxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxx>
Subject: [PATCH][doc] BASHENV -> BASH_ENV typo
Date: Tue, 5 Mar 2024 08:42:03 +0000
Archived-at: <https://zsh.org/workers/52685>
List-id: <zsh-workers.zsh.org>
Mail-followup-to: Zsh hackers list <zsh-workers@xxxxxxx>

Note that it's ~/.zshenv or $BASHOPTS, but it's $BASH_ENV, not
$BASHENV (I also often get confused as to whether underscores
are needed or not)

diff --git a/Doc/Zsh/restricted.yo b/Doc/Zsh/restricted.yo
index 7948cfe8a..a84fd28ea 100644
--- a/Doc/Zsh/restricted.yo
+++ b/Doc/Zsh/restricted.yo
@@ -68,7 +68,7 @@ If a `tt(perl)', `tt(python)', `tt(bash)', or other general purpose
 interpreted script is treated as a restricted
 command, the user can work around the restriction by
 setting specially crafted `tt(PERL5LIB)', `tt(PYTHONPATH)',
-`tt(BASHENV)' (etc.) environment variables. On GNU systems, any
+`tt(BASH_ENV)' (etc.) environment variables. On GNU systems, any
 command can be made to run arbitrary code when performing character set
 conversion (including zsh itself) by setting a `tt(GCONV_PATH)'
 environment variable.  Those are only a few examples.

Messages sorted by: Reverse Date, Date, Thread, Author