1
0
Fork 0
mirror of git://git.code.sf.net/p/zsh/code synced 2025-10-23 04:30:24 +02:00

Richard Hartmann: 26155: quote use of . for a command in text

This commit is contained in:
Peter Stephenson 2008-12-18 09:49:04 +00:00
parent 0414a4fd70
commit 976cb71d6f
4 changed files with 11 additions and 5 deletions

View file

@ -1130,7 +1130,7 @@ alias(rehash)(hash -r)
findex(return)
cindex(functions, returning from)
item(tt(return) [ var(n) ])(
Causes a shell function or tt(.) script to return to
Causes a shell function or `tt(.)' script to return to
the invoking script with the return status specified by var(n). If var(n)
is omitted, the return status is that of the last command
executed.
@ -1237,7 +1237,7 @@ shifted instead of the positional parameters.
)
findex(source)
item(tt(source) var(file) [ var(arg) ... ])(
Same as tt(.), except that the current directory is always searched and
Same as `tt(.)', except that the current directory is always searched and
is always searched first, before directories in tt($path).
)
module(stat)(zsh/stat)

View file

@ -186,7 +186,7 @@ function the line number is reported as zero.
The format of each element is var(filename)tt(:)var(lineno).
For functions autoloaded from a file in native zsh format, where only the
body of the function occurs in the file, or for files that have been
executed by the tt(source) or tt(.) builtins, the trace information is
executed by the tt(source) or `tt(.)' builtins, the trace information is
shown as var(filename)tt(:)var(0), since the entire file is the definition.
Most users will be interested in the information in the
@ -205,6 +205,6 @@ This array contains the names and line numbers of the callers
corresponding to the functions currently being executed.
The format of each element is var(name)tt(:)var(lineno).
Callers are also shown for sourced files; the caller is the point
where the tt(source) or tt(.) command was executed.
where the tt(source) or `tt(.)' command was executed.
)
enditem()

View file

@ -844,7 +844,7 @@ Thus if `tt(/usr/local/bin)' is in the user's path, and he or she types
(assuming it exists).
Commands explicitly beginning with `tt(/)', `tt(./)' or `tt(../)'
are not subject to the path search.
This also applies to the tt(.) builtin.
This also applies to the `tt(.)' builtin.
Note that subdirectories of the current directory are always searched for
executables specified in this form. This takes place before any search