mirror of
https://git.code.sf.net/p/zsh/code
synced 2026-01-26 11:14:28 +00:00
53775: Fix some documentation typos
This commit is contained in:
parent
2a6e69d42d
commit
87fa6d7f05
@ -1,5 +1,10 @@
|
||||
2025-11-12 Oliver Kiddle <opk@zsh.org>
|
||||
|
||||
* Lawrence Velázquez: 53775: Doc/Zsh/builtins.yo,
|
||||
Doc/Zsh/compwid.yo, Doc/Zsh/mod_ksh93.yo, Doc/Zsh/mod_private.yo,
|
||||
Doc/Zsh/mod_random.yo, Doc/Zsh/options.yo, Doc/Zsh/zle.yo, README:
|
||||
Fix some documentation typos
|
||||
|
||||
* 54071: Completion/Zsh/Type/_ps1234: fix prompt colour completion
|
||||
|
||||
* 54043, 54055 (tweaked to use "reset" as suggested by Mikael):
|
||||
|
||||
@ -870,7 +870,7 @@ can also be 0 to suppress all indentation.
|
||||
|
||||
The tt(-W) option turns on the option tt(WARN_NESTED_VAR) for the named
|
||||
function or functions only. The option is turned off at the start of
|
||||
nested functions (apart from anonoymous functions) unless the called
|
||||
nested functions (apart from anonymous functions) unless the called
|
||||
function also has the tt(-W) attribute.
|
||||
|
||||
The tt(-c) option causes var(oldfn) to be copied to var(newfn). The
|
||||
@ -1631,7 +1631,7 @@ cindex(functions, returning from)
|
||||
item(tt(return) [ var(n) ])(
|
||||
Causes a shell function or `tt(.)' script to return to
|
||||
the invoking script with the return status specified by
|
||||
an arithmetic expression var(n). Also causes a non-interctive
|
||||
an arithmetic expression var(n). Also causes a non-interactive
|
||||
shell to exit, allowing files containing shell code to be used
|
||||
both as scripts and as autoloadable shell functions.
|
||||
For example, the following prints `tt(42)':
|
||||
|
||||
@ -944,7 +944,7 @@ The patterns before the `tt(=)' are used to match substrings of the current
|
||||
word. For each matched substring, the corresponding part of the match pattern
|
||||
is broadened with the pattern after the `tt(=)', by means of a logical tt(OR).
|
||||
|
||||
Each pattern in a matcher cosists of either
|
||||
Each pattern in a matcher consists of either
|
||||
|
||||
startitemize()
|
||||
itemiz(the empty string or)
|
||||
@ -1103,7 +1103,7 @@ anchors, below), then var(match-pat) may also be `tt(*)' or `tt(**)'. `tt(*)'
|
||||
can match any part of a completion that does not contain any substrings
|
||||
matching var(anchor), whereas a `tt(**)' can match any part of a completion,
|
||||
period. (Note that this is different from the behavior of `tt(*)' in the
|
||||
anchorless forms of `tt(l:)' and `tt(r:)' and and also different from `tt(*)'
|
||||
anchorless forms of `tt(l:)' and `tt(r:)' and also different from `tt(*)'
|
||||
and `tt(**)' in glob expressions.)
|
||||
|
||||
startitem()
|
||||
|
||||
@ -132,7 +132,7 @@ em(THIS FEATURE IS NOT YET IMPLEMENTED.)
|
||||
)
|
||||
item(tt(.sh.math) <K>)(
|
||||
This parameter is more accurately considered a namespace. A function
|
||||
defintion of the form
|
||||
definition of the form
|
||||
ifzman()
|
||||
indent(tt(function .sh.math.)var(name)tt( )var(ident)tt( ... { )var(list)tt( }))
|
||||
|
||||
|
||||
@ -96,7 +96,7 @@ may use the private parameter because those have the same calling scope.)
|
||||
enditemize()
|
||||
|
||||
Note that this differs from the static scope defined by compiled languages
|
||||
derived from C, in that the a new call to the same function creates a new
|
||||
derived from C, in that a new call to the same function creates a new
|
||||
scope, i.e., the parameter is still associated with the call stack rather
|
||||
than with the function definition. It differs from ksh `tt(typeset -S)'
|
||||
because the syntax used to define the function has no bearing on whether
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
COMMENT(!MOD!zsh/random
|
||||
Some High-quality randomness parameters and functions.
|
||||
Some high-quality randomness parameters and functions.
|
||||
!MOD!)
|
||||
The tt(zsh/random) module gets random data from the kernel random pool. If no
|
||||
kernel random pool can be found, the module will not load.
|
||||
|
||||
@ -2138,7 +2138,7 @@ pindex(NOKSHTYPESET)
|
||||
cindex(argument splitting, in typeset etc.)
|
||||
cindex(ksh, argument splitting in typeset)
|
||||
item(tt(KSH_TYPESET))(
|
||||
This option is now obsolete: a better appropximation to the behaviour of
|
||||
This option is now obsolete: a better approximation to the behaviour of
|
||||
other shells is obtained with the reserved word interface to
|
||||
tt(declare), tt(export), tt(float), tt(integer), tt(local), tt(readonly)
|
||||
and tt(typeset). Note that the option is only applied when the reserved
|
||||
@ -2284,7 +2284,7 @@ for example in expressions such as tt($#-) and tt($#*).
|
||||
Another difference is that with the option set assignment to an
|
||||
unset variable in arithmetic context causes the variable to be created
|
||||
as a scalar rather than a numeric type. So after `tt(unset t; (( t = 3
|
||||
)))'. without tt(POSIX_IDENTIFIERS) set tt(t) has integer type, while with
|
||||
)))', without tt(POSIX_IDENTIFIERS) set tt(t) has integer type, while with
|
||||
it set it has scalar type.
|
||||
|
||||
When the option is unset and multibyte character support is enabled (i.e. it
|
||||
|
||||
@ -2563,7 +2563,7 @@ tt(command) keymap, and if not found there in the main keymap.
|
||||
tindex(which-command)
|
||||
item(tt(which-command) (tt(ESC-?)) (unbound) (unbound))(
|
||||
Push the buffer onto the buffer stack, and execute the
|
||||
command `tt(which-command) var(cmd)'. where var(cmd) is the current
|
||||
command `tt(which-command) var(cmd)', where var(cmd) is the current
|
||||
command. tt(which-command) is normally aliased to tt(whence).
|
||||
)
|
||||
tindex(vi-digit-or-beginning-of-line)
|
||||
|
||||
2
README
2
README
@ -88,7 +88,7 @@ consistent and better aligned with the POSIX-2017 specification of
|
||||
echo "This is printed only prior to 5.10."
|
||||
|
||||
- The `&&` and `||` operators now always ignore ERR_RETURN in their
|
||||
left operand. Until this version, the operators failed to ignored
|
||||
left operand. Until this version, the operators failed to ignore
|
||||
ERR_RETURN in their left operand if they were executed as part of
|
||||
a function call or an anonymous function that was itself executed
|
||||
in a context where ERR_RETURN is ignored. Example:
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user