* Minimal patch against the docs
@ 2008-12-18 0:26 Richard Hartmann
0 siblings, 0 replies; only message in thread
From: Richard Hartmann @ 2008-12-18 0:26 UTC (permalink / raw)
To: Zsh Workers
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
Hi all,
I noticed that `tt(.)' is not always used in normal text. Of course,
tt(.) makes more sense in any syntax examples & lists so I did not touch
that part. Patch is trivial & self-explanatory.
Richard
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: documentation_dot_clarification.patch --]
[-- Type: text/x-diff; name=documentation_dot_clarification.patch, Size: 2573 bytes --]
diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo
index 8317c95..d4d2a4c 100644
--- a/Doc/Zsh/builtins.yo
+++ b/Doc/Zsh/builtins.yo
@@ -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)
diff --git a/Doc/Zsh/mod_parameter.yo b/Doc/Zsh/mod_parameter.yo
index 0f2c212..d553070 100644
--- a/Doc/Zsh/mod_parameter.yo
+++ b/Doc/Zsh/mod_parameter.yo
@@ -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()
diff --git a/Doc/Zsh/options.yo b/Doc/Zsh/options.yo
index 0536970..4bd82f3 100644
--- a/Doc/Zsh/options.yo
+++ b/Doc/Zsh/options.yo
@@ -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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-12-18 0:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-12-18 0:26 Minimal patch against the docs Richard Hartmann
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).