mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-03 10:21:46 +02:00
Fix some typos in the documentation
This commit is contained in:
parent
859cccba7a
commit
7eb949a6bb
7 changed files with 15 additions and 15 deletions
|
@ -603,7 +603,7 @@ tt(enable -p) reenables patterns disabled with tt(disable -p). Note
|
|||
that it does not override globbing options; for example, `tt(enable -p
|
||||
"~")' does not cause the pattern character tt(~) to be active unless
|
||||
the tt(EXTENDED_GLOB) option is also set. To enable all possible
|
||||
patterns (so that they may be invidually disabled with tt(disable -p)),
|
||||
patterns (so that they may be individually disabled with tt(disable -p)),
|
||||
use `tt(setopt EXTENDED_GLOB KSH_GLOB NO_SH_GLOB)'.
|
||||
)
|
||||
findex(eval)
|
||||
|
|
|
@ -1156,8 +1156,8 @@ item(tt(vcs_info_hookdel))(
|
|||
Remove hook-functions from a given hook. The hook needs to be given as the
|
||||
first non-option argument; what follows is a list of hook-function
|
||||
names to un-register from the hook. If `tt(-a)' is used as the first
|
||||
argument, tt(all) occurances of the functions are unregistered. Otherwise
|
||||
only the last occurance is removed (if a function was registered to a hook
|
||||
argument, tt(all) occurrences of the functions are unregistered. Otherwise
|
||||
only the last occurrence is removed (if a function was registered to a hook
|
||||
more than once) . The `tt(+vi-)' prefix needs to be left out here. See
|
||||
bf(Hooks in vcs_info) below for details.
|
||||
)
|
||||
|
@ -1292,7 +1292,7 @@ tt(vcs_info) collected from `hg'.
|
|||
|
||||
When setting tt(ret) to non-zero, the string in
|
||||
tt(${hook_com[hg-bookmark-string]}) will be used in the tt(%m) escape in
|
||||
tt(formats) and tt(actionformats) and will be availabe in the global
|
||||
tt(formats) and tt(actionformats) and will be available in the global
|
||||
tt(backend_misc) array as tt(${backend_misc[bookmarks]}).
|
||||
)
|
||||
item(tt(gen-applied-string))(
|
||||
|
@ -2965,7 +2965,7 @@ types even if they are executable. As this example shows, the complete
|
|||
file name is matched against the pattern, regardless of how the file
|
||||
was passed to the handler. The file is resolved to a full path using
|
||||
the tt(:A) modifier described in
|
||||
ifzman(the subsection Modifers in zmanref(zshexpn))\
|
||||
ifzman(the subsection Modifiers in zmanref(zshexpn))\
|
||||
ifnzman(noderef(Modifiers));
|
||||
this means that symbolic links are resolved where possible, so that
|
||||
links into other file systems behave in the correct fashion.
|
||||
|
|
|
@ -316,7 +316,7 @@ the rightmost `tt(?)' in a context scan can similarly be omitted. Note
|
|||
the same record of the last var(l) and var(r) is maintained across all
|
||||
forms of expansion.
|
||||
|
||||
Note that if a `tt(&)' is used within glob qualifers an extra backslash
|
||||
Note that if a `tt(&)' is used within glob qualifiers an extra backslash
|
||||
is needed as a tt(&) is a special character in this case.
|
||||
|
||||
If the option tt(HIST_SUBST_PATTERN) is set, var(l) is treated as
|
||||
|
@ -475,7 +475,7 @@ spawned from the parent shell which will wait for their completion.
|
|||
Another problem arises any time a job with a substitution that requires
|
||||
a temporary file is disowned by the shell, including the case where
|
||||
`tt(&!)' or `tt(&|)' appears at the end of a command containing a
|
||||
subsitution. In that case the temporary file will not be cleaned up as
|
||||
substitution. In that case the temporary file will not be cleaned up as
|
||||
the shell no longer has any memory of the job. A workaround is to use
|
||||
a subshell, for example,
|
||||
|
||||
|
@ -632,7 +632,7 @@ quoted, the elements of var(arrayname) are instead tested against the
|
|||
entire expression.
|
||||
)
|
||||
item(tt(${)var(name)tt(:*)var(arrayname)tt(}))(
|
||||
Similar to the preceding subsitution, but in the opposite sense,
|
||||
Similar to the preceding substitution, but in the opposite sense,
|
||||
so that entries present in both the original substitution and as
|
||||
elements of var(arrayname) are retained and others removed.
|
||||
)
|
||||
|
@ -701,7 +701,7 @@ print ${foo:$(( 1 + 2))}
|
|||
print ${foo:$(echo 1 + 2)})
|
||||
|
||||
all have the same effect, extracting the string starting at the fourth
|
||||
character of tt($foo) if the substution would otherwise return a scalar,
|
||||
character of tt($foo) if the substitution would otherwise return a scalar,
|
||||
or the array starting at the fourth element if tt($foo) would return an
|
||||
array. Note that with the option tt(KSH_ARRAYS) tt($foo) always returns
|
||||
a scalar (regardless of the use of the offset syntax) and a form
|
||||
|
@ -924,7 +924,7 @@ that result from field splitting.
|
|||
item(tt(D))(
|
||||
Assume the string or array elements contain directories and attempt
|
||||
to substitute the leading part of these by names. The remainder of
|
||||
the path (the whole of it if the leading part was not subsituted)
|
||||
the path (the whole of it if the leading part was not substituted)
|
||||
is then quoted so that the whole string can be used as a shell
|
||||
argument. This is the reverse of `tt(~)' substitution: see
|
||||
ifnzman(noderef(Filename Expansion))\
|
||||
|
|
|
@ -265,7 +265,7 @@ string var(array) is interpreted as the name of another var(spec),
|
|||
which is used to choose where to store the values. If no other var(spec)
|
||||
is found, the values are stored as usual. This changes only the way the
|
||||
values are stored, not the way tt($*) is parsed, so results may be
|
||||
unpredicable if the `var(name)tt(+)' specifier is used inconsistently.
|
||||
unpredictable if the `var(name)tt(+)' specifier is used inconsistently.
|
||||
)
|
||||
item(tt(-E))(
|
||||
This changes the parsing rules to em(not) stop at the first string
|
||||
|
|
|
@ -1780,7 +1780,7 @@ cindex(tracing, of commands)
|
|||
cindex(commands, tracing)
|
||||
item(tt(XTRACE) (tt(-x), ksh: tt(-x)))(
|
||||
Print commands and their arguments as they are executed. The
|
||||
output is proceded by the value of tt($PS4), formatted as described
|
||||
output is preceded by the value of tt($PS4), formatted as described
|
||||
in
|
||||
ifzman(the section EXPANSION OF PROMPT SEQUENCES in zmanref(zshmisc))\
|
||||
ifnzman(noderef(Prompt Expansion)).
|
||||
|
@ -2079,7 +2079,7 @@ variables, or in arguments to external programs.
|
|||
|
||||
When this option is set, the tt($')var(...)tt(') expression is truncated at
|
||||
the null character. Note that remaining parts of the same string
|
||||
beyond the termination of the quotes are not trunctated.
|
||||
beyond the termination of the quotes are not truncated.
|
||||
|
||||
For example, the command line argument tt(a$'b\0c'd) is treated with
|
||||
the option off as the characters tt(a), tt(b), null, tt(c), tt(d),
|
||||
|
|
|
@ -1042,7 +1042,7 @@ backquotes only. Should the chosen character be one of singlequote,
|
|||
doublequote or backquote, there must also be an odd number of them
|
||||
on the command line for the last one to be removed.
|
||||
|
||||
For backward compabitility, if the tt(SUNKEYBOARDHACK) option is
|
||||
For backward compatibility, if the tt(SUNKEYBOARDHACK) option is
|
||||
explicitly set, the value of tt(KEYBOARD_HACK) reverts to backquote.
|
||||
If the option is explicitly unset, this variable is set to empty.
|
||||
)
|
||||
|
|
|
@ -2315,7 +2315,7 @@ These characters are described below.
|
|||
)
|
||||
cindex(completion removable suffix, highlighting)
|
||||
cindex(suffix, highlighting removable, in completion)
|
||||
cindex(removable suffix, highlighting in completino)
|
||||
cindex(removable suffix, highlighting in completion)
|
||||
item(tt(suffix))(
|
||||
This context is used in completion for characters that are
|
||||
marked as suffixes that will be removed if the completion ends
|
||||
|
|
Loading…
Reference in a new issue