mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-05-20 23:41:27 +02:00
52685: fix typo in the name of bash's BASH_ENV variable.
This commit is contained in:
parent
c0a392b392
commit
b56250e9b9
2 changed files with 6 additions and 1 deletions
|
@ -1,3 +1,8 @@
|
|||
2024-03-05 Stephane Chazelas <stephane@chazelas.org>
|
||||
|
||||
* 52685: Doc/Zsh/restricted.yo: fix typo in the name of bash's
|
||||
BASH_ENV variable.
|
||||
|
||||
2024-03-04 Bart Schaefer <schaefer@zsh.org>
|
||||
|
||||
* unposted (cf. 52615): Src/builtin.c: use META_NOALLOC for 52591
|
||||
|
|
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue