From b56250e9b99d9cd0e70261ff6e7f6f33583c1b04 Mon Sep 17 00:00:00 2001 From: Stephane Chazelas Date: Tue, 5 Mar 2024 19:57:35 +0000 Subject: 52685: fix typo in the name of bash's BASH_ENV variable. --- ChangeLog | 5 +++++ Doc/Zsh/restricted.yo | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index b4ebfedbc..68f826342 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2024-03-05 Stephane Chazelas + + * 52685: Doc/Zsh/restricted.yo: fix typo in the name of bash's + BASH_ENV variable. + 2024-03-04 Bart Schaefer * unposted (cf. 52615): Src/builtin.c: use META_NOALLOC for 52591 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. -- cgit 1.4.1