Attachment "pat.manpages" to
ticket [1610310fff]
added by
lvirden
2006-12-07 01:08:36.
--- chan.n.bak Wed Dec 6 02:02:56 2006
+++ chan.n Wed Dec 6 12:46:06 2006
@@ -354,3 +354,3 @@
thread, even if the channel was moved into a different thread. To this
-end all invokations of the handler are forwarded to the original
+end all invocations of the handler are forwarded to the original
thread by posting special events to it. This means that the original
@@ -386,3 +386,3 @@
\fIchannelId\fR failed because the end of the data stream was reached,
-returning 1 if end-fo-file was reached, and 0 otherwise.
+returning 1 if end-of-file was reached, and 0 otherwise.
.TP
--- clock.n.bak Mon Jul 31 02:01:48 2006
+++ clock.n Wed Dec 6 12:33:33 2006
@@ -90,3 +90,3 @@
\fBdays\fR, \fBweeks\fR, \fBmonths\fR, or \fByears\fR, or
-any unique prefix of such a word. Used in conjuction with \fIcount\fR
+any unique prefix of such a word. Used in conjunction with \fIcount\fR
to identify an interval of time, for example, \fI3 seconds\fR or
@@ -269,3 +269,3 @@
epoch time, and \fBclock microseconds\fR returns the count of microseconds
-from the epoch time. In addition, there js a \fBclock clicks\fR command
+from the epoch time. In addition, there is a \fBclock clicks\fR command
that returns a platform-dependent high-resolution timer. Unlike
@@ -707,3 +707,3 @@
\fB%%\fR
-On output, produces a literal '\fB%\fR' charater. On input, matches
+On output, produces a literal '\fB%\fR' character. On input, matches
a literal '\fB%\fR' character.
--- eval.n.bak Fri Nov 3 02:02:50 2006
+++ eval.n Wed Dec 6 12:34:45 2006
@@ -55,3 +55,3 @@
actually just a list of words forming a command prefix), it is better
-to use \fB{*}$script\fR when doing this sort of invokation
+to use \fB{*}$script\fR when doing this sort of invocation
pattern. It is less general than the \fBeval\fR command, and hence
--- exit.n.bak Sat Nov 20 02:02:08 2004
+++ exit.n Wed Dec 6 12:35:06 2006
@@ -28,3 +28,3 @@
the calling process, the \fBexit\fR command is an important part of
-signalling that something fatal has gone wrong. This code fragment is
+signaling that something fatal has gone wrong. This code fragment is
useful in scripts to act as a general problem trap:
--- expr.n.bak Thu Aug 10 02:02:15 2006
+++ expr.n Wed Dec 6 12:35:26 2006
@@ -249,3 +249,3 @@
in those calculations where values overflowed the range of those types.
-Any code that relied on these implicit trunctions will need to explicitly
+Any code that relied on these implicit truncations will need to explicitly
add \fBint()\fR or \fBwide()\fR function calls to expressions at the points
--- interp.n.bak Fri Nov 3 02:02:50 2006
+++ interp.n Wed Dec 6 12:38:11 2006
@@ -690,3 +690,3 @@
executing. If the callback generates an error, it is reported through
-the background error mechansism (see \fBBACKGROUND ERROR HANDLING\fR).
+the background error mechanism (see \fBBACKGROUND ERROR HANDLING\fR).
Note that the
@@ -709,3 +709,3 @@
\fB\-seconds\fR option (whether it was set previously or is being set
-this invokation.)
+this invocation.)
.TP
@@ -746,3 +746,3 @@
A background error handler consists of a non-empty list of words to
-which will, at invokation time, be appended two further words. The
+which will, at invocation time, be appended two further words. The
first word will be the error message string, and the second will a
@@ -764,3 +764,3 @@
Executing an arbitrary command in a safe interpreter where every
-invokation of \fBlappend\fR is logged:
+invocation of \fBlappend\fR is logged:
.CS
@@ -770,3 +770,3 @@
proc loggedLappend {i args} {
- puts "logged invokation of lappend $args"
+ puts "logged invocation of lappend $args"
\fBinterp invokehidden\fR $i lappend {*}$args
--- open.n.bak Thu Jun 8 02:48:43 2006
+++ open.n Wed Dec 6 12:40:19 2006
@@ -90,3 +90,3 @@
\fBBINARY\fR
-Configure the opened channed with the \fB-translation binary\fR option.
+Configure the opened channel with the \fB-translation binary\fR option.
.VE 8.5
--- platform_shell.n.bak Tue Dec 5 20:42:00 2006
+++ platform_shell.n Wed Dec 6 12:40:38 2006
@@ -34,6 +34,6 @@
While for most platform this means that the architecture of the
-interogated shell is identical to the architecture of the running
+interrogated shell is identical to the architecture of the running
shell this is not generally true. A counter example are all platforms
which have 32 and 64 bit variants and where a 64bit system is able to
-run 32bit code. For these running and interogated shell may have
+run 32bit code. For these running and interrogated shell may have
different 32/64 bit settings and thus different identifiers.
--- pwd.n.bak Thu Oct 28 02:02:00 2004
+++ pwd.n Wed Dec 6 12:40:44 2006
@@ -26,3 +26,3 @@
the application usually running in the directory that it was started
-in (unless the user specifies otherwise) since that minimises user
+in (unless the user specifies otherwise) since that minimizes user
confusion. The way to do this is to save the current directory while
--- refchan.n.bak Sat Jul 29 02:01:50 2006
+++ refchan.n Wed Dec 6 12:41:23 2006
@@ -34,3 +34,3 @@
.
-An invokation of this subcommand will be the first call the
+An invocation of this subcommand will be the first call the
\fIcmdPrefix\fR will receive for the specified new \fIchannelId\fR. It
@@ -64,3 +64,3 @@
.
-An invokation of this subcommand will be the last call the
+An invocation of this subcommand will be the last call the
\fIcmdPrefix\fR will receive for the specified \fIchannelId\fR. It will
@@ -100,3 +100,3 @@
event which was not listed in the last call to \fBwatch\fR will cause
-\fBchan postenvent\fR to throw an error.
+\fBchan postevent\fR to throw an error.
.RE
@@ -114,3 +114,3 @@
\fIbytes\fR. If the returned data contains more bytes than requested,
-an error will be signalled and later thrown by the command which
+an error will be signaled and later thrown by the command which
performed the read (usually \fBgets\fR or \fBread\fR). However,
--- regsub.n.bak Wed May 11 02:02:01 2005
+++ regsub.n Wed Dec 6 12:41:46 2006
@@ -121,3 +121,3 @@
Insert double-quotes around the first instance of the word
-\fBinteresting\fR, however it is capitalised.
+\fBinteresting\fR, however it is capitalized.
.CS
--- scan.n.bak Thu Jun 15 02:03:22 2006
+++ scan.n Wed Dec 6 12:51:05 2006
@@ -82,6 +82,6 @@
command. The \fBL\fR size modifier is equivalent to the \fBl\fR size
-modifer. Either one indicates the integer range to be stored is
+modifier. Either one indicates the integer range to be stored is
limited to the same range produced by the \fBwide()\fR function of
the \fBexpr\fR command. The \fBll\fR size modifier indicates that
-the integer range ro be stored is unlimited.
+the integer range to be stored is unlimited.
.VE 8.5
@@ -110,4 +110,4 @@
range is computed and stored in the variable as a decimal string.
-The conversion makes no sense without refernce to a truncation range,
-so the size modifer \fBll\fR is not permitted in combination
+The conversion makes no sense without reference to a truncation range,
+so the size modifier \fBll\fR is not permitted in combination
with conversion character \fBu\fR.
@@ -161,3 +161,3 @@
If the first or last character between the brackets is a \fB\-\fR, then
-it is treated as part of \fIchars\fR rather than indicating a ranvaluege.
+it is treated as part of \fIchars\fR rather than indicating a range value.
.TP 10
--- tclvars.n.bak Wed Dec 6 02:02:56 2006
+++ tclvars.n Wed Dec 6 12:44:37 2006
@@ -379,3 +379,3 @@
.PP
-The \fBwish\fR executably additionally specifies the following global
+The \fBwish\fR executable additionally specifies the following global
variable:
--- tm.n.bak Sat Nov 13 02:02:02 2004
+++ tm.n Wed Dec 6 12:44:48 2006
@@ -68,3 +68,3 @@
.PP
-The command has been exposed to allow a buildsystem to define
+The command has been exposed to allow a build system to define
additional root paths beyond those described by this document.
--- unload.n.bak Wed May 11 02:02:01 2005
+++ unload.n Wed Dec 6 12:45:10 2006
@@ -43,3 +43,3 @@
\fB\-nocomplain\fR
-Supresses all error messages. If this switch is given \fBunload\fR will
+Suppresses all error messages. If this switch is given \fBunload\fR will
never report an error.
@@ -61,3 +61,3 @@
call on the file), these counters track how many interpreters use the library.
-Each subsequent call to \fBload\fR after the first, simply increaments the
+Each subsequent call to \fBload\fR after the first, simply increments the
proper reference count.
