summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordgp <dgp@users.sourceforge.net>2015-06-08 17:17:14 (GMT)
committerdgp <dgp@users.sourceforge.net>2015-06-08 17:17:14 (GMT)
commitf5b6f91e7a334f96572f303116009f8d1304bed4 (patch)
treee366beb4438408da1f0ecc72b820ac53770ab6da
parentd5216492533d69d423a9b113cb23a024ea2d500f (diff)
downloadtcl-f5b6f91e7a334f96572f303116009f8d1304bed4.zip
tcl-f5b6f91e7a334f96572f303116009f8d1304bed4.tar.gz
tcl-f5b6f91e7a334f96572f303116009f8d1304bed4.tar.bz2
Stop telling lie about command delete traces.
-rw-r--r--doc/TraceCmd.32
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/TraceCmd.3 b/doc/TraceCmd.3
index 7ff26e4..ed7f365 100644
--- a/doc/TraceCmd.3
+++ b/doc/TraceCmd.3
@@ -76,7 +76,7 @@ created. \fIClientData\fR typically points to an application-specific
data structure that describes what to do when \fIproc\fR is invoked.
\fIOldName\fR gives the name of the command being renamed, and
\fInewName\fR gives the name that the command is being renamed to (or
-an empty string or NULL when the command is being deleted.)
+NULL when the command is being deleted.)
\fIFlags\fR is an OR'ed combination of bits potentially providing
several pieces of information. One of the bits \fBTCL_TRACE_RENAME\fR and
\fBTCL_TRACE_DELETE\fR will be set in \fIflags\fR to indicate which