From e5eb094bf3c031f07f7e9ab152fe63a120dd3821 Mon Sep 17 00:00:00 2001 From: Oliver Kiddle Date: Mon, 8 May 2000 18:14:46 +0000 Subject: minor doc fixes (11268) --- Doc/Zsh/builtins.yo | 8 ++++---- Doc/Zsh/compsys.yo | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) (limited to 'Doc') diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo index 31e94805b..a65ff4717 100644 --- a/Doc/Zsh/builtins.yo +++ b/Doc/Zsh/builtins.yo @@ -1026,13 +1026,13 @@ the former. Only the scalar may have an initial value. Both the scalar and the array may otherwise be manipulated as normal. If one is unset, the other will automatically be unset too. There is no way of untying the variables without unsetting them, or converting the -type of one them with another tt(typeset) command; tt(+T) does not work, -assigning an array to var(SCALAR) is an error, and assigning a scalar -to var(array) sets it to be a single-element array. Note that +type of one of them with another tt(typeset) command; tt(+T) does not +work, assigning an array to var(SCALAR) is an error, and assigning a +scalar to var(array) sets it to be a single-element array. Note that both tt(typeset -xT ...) and tt(export -T ...) work, but only the scalar will be marked for export. -The flag tt(-g) (global) flag is treated specially: it means that any +The tt(-g) (global) flag is treated specially: it means that any resulting parameter will not be restricted to local scope. Note that this does not necessarily mean that the parameter will be global, as the flag will apply to any existing parameter (even if unset) from an enclosing diff --git a/Doc/Zsh/compsys.yo b/Doc/Zsh/compsys.yo index cdfb681bc..ed7de1411 100644 --- a/Doc/Zsh/compsys.yo +++ b/Doc/Zsh/compsys.yo @@ -1182,7 +1182,7 @@ is set to `true', then none of the words that are already on the line will be considered possible completions. Note that you almost certainly don't want to set this for a general -context such as `tt(:completion:*)'. This because it would disallow +context such as `tt(:completion:*)'. This is because it would disallow completion of, for example, options multiple times even if the command in question accepts the option more than once. ) -- cgit 1.4.1