about summary refs log tree commit diff
path: root/Etc/FAQ.yo
diff options
context:
space:
mode:
authorPeter Stephenson <pws@users.sourceforge.net>2008-12-10 09:52:32 +0000
committerPeter Stephenson <pws@users.sourceforge.net>2008-12-10 09:52:32 +0000
commit63e60d3d21ebfd985d83a5359b8e5bc68de5dcaf (patch)
tree1668ac684ba8ee59be33a119557954e3267f1842 /Etc/FAQ.yo
parent02f05d746223c73981f3564ff21b324bb222e41a (diff)
downloadzsh-63e60d3d21ebfd985d83a5359b8e5bc68de5dcaf.tar.gz
zsh-63e60d3d21ebfd985d83a5359b8e5bc68de5dcaf.tar.xz
zsh-63e60d3d21ebfd985d83a5359b8e5bc68de5dcaf.zip
users/13566: note you cant unset array elements
Diffstat (limited to 'Etc/FAQ.yo')
-rw-r--r--Etc/FAQ.yo6
1 files changed, 6 insertions, 0 deletions
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index 1cf3cae49..1ba9ed38f 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -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