mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-02 10:01:11 +02:00
users/13566: note you cant unset array elements
This commit is contained in:
parent
02f05d7462
commit
63e60d3d21
2 changed files with 11 additions and 0 deletions
|
@ -1,3 +1,8 @@
|
|||
2008-12-10 Peter Stephenson <pws@csr.com>
|
||||
|
||||
* users/13566: Etc/FAQ.yo: note problem with unsetting elements
|
||||
of regular arrays.
|
||||
|
||||
2008-12-09 Peter Stephenson <pws@csr.com>
|
||||
|
||||
* 26119: Doc/Zsh/zle.yo, Src/Zle/zle_main.c: option to allow vared
|
||||
|
|
|
@ -541,6 +541,12 @@ tt(SH_OPTION_LETTERS),
|
|||
mytt($array) refers to the whole array, not tt($array[0]);
|
||||
braces are unnecessary: tt($a[1] == ${a[1]}), etc.
|
||||
Set the tt(KSH_ARRAYS) option for compatibility.
|
||||
it() Furthermore, individual elements of arrays in zsh are always
|
||||
strings, not separate parameters. This means, for example, you
|
||||
can't `unset' an array element in zsh as you can in ksh; you
|
||||
can only set it to the empty string, or shorten the array.
|
||||
(You can unset elements of associative arrays in zsh because
|
||||
those are a completely different type of object.)
|
||||
it() Coprocesses are established by mytt(coproc); mytt(|&) behaves like
|
||||
csh. Handling of coprocess file descriptors is also different.
|
||||
it() In mytt(cmd1 && cmd2 &), only mytt(cmd2) instead of the whole
|
||||
|
|
Loading…
Reference in a new issue