Triage of 818 open and Pending Bug tickets of Tcl with no comment or check-in from me on 2026-10-16 (in Tcl's workflow Pending means "resolved, waiting for confirmation"). Reproduced on Linux (main 9.1 tip, 9.0 tip, 8.7b1, 8.6 tip, 8.5, 8.4 and old releases), on FreeBSD, NetBSD, OpenBSD and OpenIndiana VMs for platform tickets, and on a Windows 11 VM. Rows marked patch link to a prototype patch (287 in all, in tcl-triage/prototypes). Updated 2026-11-11: the emoji before each ticket id shows its progress.
e4c24e86b5.patch: VERIFIED
\fB monotonic\fR (stray space) and line 133 the unindented .LP Note that the output differs from after info. (the other typos from the ticket are already fixed on main)
man -l timer.n shows the note indented under the timer info item; troff warnings unchanged (1, pre-existing)
DOCS (mostly fixed on main; one item left)
after ms script and "Wall clock events" paragraphs was fixed by the .RS/.PP blocks cherry-picked in 151d53761e (2026-09-07). The only item left: "Note that the output differs from after info." still sits after the event-loop paragraph at the end of DESCRIPTION, not under timer info. (timer exists only in 9.1.)
timer info item as an .RS/.PP block; also fixes the stray space in \fB monotonic). Checked with man -l.
07000bd237.patch: VERIFIED
groff -man -Tutf8 doc/IntObj.3 renders both new paragraphs; no new warnings (only the usual man.macros ones).
DOCS
oo::define classvariable; classvariable is a method-body command documented in classvariable(n), which the …858a615194.patch: VERIFIED
oo::define oo::object classvariable x -> invalid command name "classvariable"; classvariable exists only as ::oo::Helpers::classvariable (documented in doc/classvariable.n), and define.n uses it in the TIP 478 example without saying so or listing it in SEE ALSO
man -l define.n renders the new sentence before the example and classvariable(n) in SEE ALSO
DOCS (partly NOT-A-BUG: there is no oo::define classvariable; classvariable is a method-body command documented in classvariable(n), which the define.n example uses without saying so)
oo::define oo::object classvariable x -> invalid command name; ::oo::define::* has no classvariable.
81ebe684b4.patch: VERIFIED
DOCS (confirmed in main, 9.0, 8.6 sources)
78f4421436.patch: VERIFIED
objPtr->bytes == NULL || bytes == NULL, Tcl_AttemptAlloc/Realloc, always NUL-terminated, returns NULL on failure, Tcl_FreeInternalRep = TclFreeInternalRep): accurate. troff warnings unchanged (1, pre-existing)
DOCS (partly addressed: 8f9c7f5fd8, 2025-05-02, on main only; 9.0 still lacks it; 8.6 has no such API)
31fedb885e.patch: VERIFIED
testexprlong {} -> This is a result: 0 (TCL_OK), testexprdouble {} -> 0.0, testexprstring {} -> 0, while testexprlongobj {} and expr {} -> empty expression; doc/ExprLong.3 does not mention it
man -l doc/ExprLong.3 renders the new paragraph correctly and it matches the observed behaviour
DOCS (behaviour confirmed in main, 9.0 and 8.6 by reading the code)
copy is a shorter, partly different text)DOCS (still open: doc/fcopy.n is standalone, doc/chan.n copy is a shorter, partly different text)
fcopy -size 2).
fcopy -size 2 copies 2 characters with both strict and tcl8; only 8.6 copied bytes. Apart from that, fcopy.n is a superset of chan.n (translation, encoding/profile, EILSEQ recovery), so its text can move into chan.n and fcopy.n can reference it.
a97680cbed.patch: VERIFIED
groff -man -Tutf8 doc/FileSystem.3 renders the new text
DOCS (still outdated in main, 9.0, 8.6)
5c2f6c2ff4.patch: VERIFIED
tcltest 5c2f.tcl -> info body tcl_endOfWord and info default ... -> "tcl_endOfWord" isn't a procedure, info procs tcl_end* empty; after auto_load tcl_endOfWord -> tcl_endOfWord, args str start. Behaviour as the new text describes; info.n says nothing about it
man -l info.n renders the new sentences under info procs
DOCS (behaviour by design; REPRODUCED on main, 8.6)
info body tcl_endOfWord errors "isn't a procedure" and info procs tcl_end* is empty until the proc is called.
auto_index until unknown/auto_load sources them; info (generic/tclCmdIL.c) looks only at existing commands. Intended.
info procs paragraph mentions not-yet-loaded procs and auto_load)
info procs/args/body/default don't see them. Proposed doc note in info.n pointing to auto_load.
21e3c44ac9.patch: VERIFIED
unsigned short toUnicode/fromUnicode (256-entry pages keyed by the lead byte), and encoding convertto shiftjis \U1F600 -> unexpected character at index 0: 'U+01F600' (with -profile replace -> ?), so the documented limit is real
man -l doc/Encoding.3 renders the new paragraph under ENCODING FILES
DOCS
unsigned short pages indexed by the high byte, so .enc table encodings are limited to 1–2 byte sequences and BMP characters (anything above U+FFFF goes to the fallback). doc/Encoding.3 only implies it ("2-byte Unicode", "double-byte numbers").
6e156333bc.patch: VERIFIED
DOCS
e7dea09f58.patch: VERIFIED
\fITheCmdNRObjProc\fR without (, "a a wrapper", Tcl_NRCallObjProc in the text vs Tcl_NRCallObjProc2 in the code, "possible implement"
groff -man -ww gives only the usual man.macros warnings. chw's androwish diff (linked in the ticket) could not be compared (no network).
DOCS (still present on main, 9.0, 8.6)
TheCmdNRObjProc is missing its (; "a a wrapper"; the text says Tcl_NRCallObjProc while the code calls Tcl_NRCallObjProc2; Tcl_EvalObjEx/Tcl_NREvalObj are italic instead of bold; "possible implement".
f4c118f67c.patch: VERIFIED
-timezone akst=-0900 akdt=-0800 fwt=+0100 fst=+0200 kst=+0900 jdt/kdt=+1000 cst=-0600 ist=+0530 a=+0100 z=+0000, j -> time zone ":j" not found (free-form scan accepts the same ones)
DOCS (still valid: clock.n TIME ZONES lists only the legacy abbreviations and gives no guidance on which location names to use; the list is also out of date)
man -l. Side note: the tzdata path in the text is the odd "/no_backup/tools/lib/tcl9.0/clock/tzdata" (tcl8.5 in 8.6)
3c05b4568a.patch: VERIFIED
Tcl_EvalObj(interp, objPtr) (deprecated block); doc/Eval.3 does not mention it at all
man -l doc/Eval.3 shows Tcl_EvalObj in NAME and SYNOPSIS and the new "older procedure that is now deprecated ... equivalent to Tcl_EvalObjEx with flags set to 0" paragraph
DOCS (still missing on main, 9.0, 8.6)
Tcl_EvalObjEx(interp, objPtr, 0) in generic/tclDecls.h (main: "Deprecated Tcl procedures" block; also in 9.0 and 8.6), but doc/Eval.3 lists only its sibling Tcl_GlobalEvalObj (NAME, SYNOPSIS and the "older procedures that are now deprecated" paragraph). It was dropped from the docs in f3b32fb71c (1999).
tcl::pkgconfig get libdir,runtime)3121e79060.patch: VERIFIED
64bit described as "a 64-bit build; on Unix only when configured with --enable-64bit" (TCL_CFG_DO64BIT is also set by the Windows makefiles for x64; on 64-bit Linux the key is 0) (52 lines now)
tcl::pkgconfig list on the tip build gives exactly the keys the page lists (8 booleans, 5 dirs x install/runtime, dllfile,runtime); get nokey -> error key not known; groff -man -Tutf8 -ww doc/pkgconfig.n renders without warnings beyond the missing man.macros
DOCS (still missing in main/9.0/8.6; only RegConfig.3 describes the generic list/get interface, tm.n mentions tcl::pkgconfig get libdir,runtime)
9b3ca8dcad.patch: VERIFIED
unset auto_path; set auto_index(zz) {proc zz {} {return ok}}: auto_load zz -> 1 (zz -> ok), auto_load parray -> 0 (no TCLLIBPATH/library fallback, as the doc claims); TCLLIBPATH=/nonexist/x -> auto_path starts with /nonexist/x <wt>/library ... (initialized at startup). main and 8.6.
DOCS (confirmed on main, 9.0, 8.6, 8.4)
auto_path unset and env(TCLLIBPATH) pointing to a dir with a tclIndex, auto_load returns 0 on all versions. It does not fall back to TCLLIBPATH or the library dir.
auto_path does not exist (if {![info exists auto_path]} {return 0}); TCLLIBPATH is only used by tcl::InitAutoPath at startup (as tclvars.n and library.n's env(TCLLIBPATH) entry already say).
994f9d7a20.patch: VERIFIED
testparsevar on the tip: {$} -> {$} {}, {$ x} -> {$} { x}, {$.} -> {$} ., {$x} -> 5 {}; doc/ParseCmd.3 does not mention the lone-$ result
groff -man -Tutf8 doc/ParseCmd.3 renders the new sentence correctly; it matches the observed behaviour
DOCS (behaviour is intentional, the same on main and 8.6)
testparsevar {$}, {$ x}, {$.} on the main build and the 8.6 tip tcltest: each returns $ with termPtr just past the $.
$ is literal. doc/ParseCmd.3 only mentions "value of the variable" and NULL.
$ case.
$ without a following variable name is no substitution, same as in scripts. Proposed doc addition to ParseCmd.3 attached.
f44329748b.patch: VERIFIED
lsort -integer {abc} -> error expected integer but got "abc" on main and 8.6, so the NOTES paragraph (options do not constrain values for lists of fewer than two elements) is wrong.
DOCS (confirmed: the paragraph is wrong since 8.5 and still in main, 9.0, 8.6 lsort.n)
lsort -integer 0.0 errors on main and 8.6.18 ("expected integer but got 0.0") and returns 0.0 on 8.4.20; lsort -real abc errors on 8.6+ and is accepted on 8.4.
lsort -integer 0.0 errors). Proposed fix: drop the obsolete paragraph from lsort.n.
DOCS (claim valid; current tutorial text not checkable offline)
linsert mylist 1 x -> mylist x (name used as a literal list); linsert $mylist 1 oneandahalf gives the expected result. doc/linsert.n and lreplace.n correctly use list.
list in the synopses and $mylist in the examples.
9a829af10f.patch: VERIFIED
source -encoding utf-8 $file; under LANG=C a module holding UTF-8 é loads as U+00E9 (scan -> 233), while doc/tm.n shows plain source module_file
package provide X V;source -encoding utf-8 F; the doc's [list source -encoding utf-8 MF] keeps the page's existing simplification.)
DOCS (8.6 only; on 9.x the man page is already accurate)
source -encoding utf-8 $file, but doc/tm.n says modules are loaded with plain source module_file, which in 8.6 means the system encoding. In 9.0/9.1 tm.tcl uses plain source $file, and source defaults to utf-8 there, so the man page is right.
source -encoding utf-8 in the three examples plus one sentence saying modules are always read as utf-8)
source defaults to utf-8, so doc/tm.n is correct there. 8.6 tm.n still shows plain source. Proposed doc fix for core-8-6-branch: use source -encoding utf-8 in the examples and state that modules are always read as utf-8.
Status now: Open
doc-re-syntax-preference, not merged: Document how the first quantifier sets the preference of the whole RE (\[fe4fca32d9\]).DOCS (behaviour as described on main, 9.0, 8.6)
12 1 2 and 1234 1 234 on all three. All examples in the branch's new re_syntax.n text checked on main and 9.0: all give the documented results (incl. (?:(.+?), (.+)){1,1} -> {foo, bar} foo bar).
Status now: Open
doc-chan-push-result, not merged: Fix 7b0e690b70 and [2920003]: document that [chan push] returns the name of the channel, and that the handle passed to the transformation handler is not that DOCS (duplicate of 2920003fff; same behaviour on main, 9.0.5, 8.6.18)
3ce04c1873.patch: VERIFIED
catch {return -code error ... -errorcode {foo bar} foobar} -> code 2, errorCode stays NONE; via a proc -> code 1, errorCode foo bar
DOCS (main, 9.0, 8.6: same text)
catch {return -code error -errorinfo {Oh no!} -errorcode {foo bar} foobar} gives 2 (TCL_RETURN) and leaves ::errorInfo/::errorCode unchanged. The same return inside a proc that is caught sets both.
catch, return produces TCL_RETURN and no error. Proposed wording in doc/return.n.
197e2bf85c.patch: VERIFIED
For a frame that corresponds to a level, (to be determined).; behaviour (rdoc1.tcl): from proc b called by proc a, info frame -1/-2 give level 1 / 2 (uplevel-style, positive), and uplevel 1 {info frame 0} has no level entry
tbl info.n | troff -man -ww -z: 0 warnings before and after; man -l renders the paragraph correctly
DOCS (8.6 text is wrong; on 9.0/9.1 the entry now just says "(to be determined)")
level present for the eval frames too). Inside uplevel #0, the frames of the uplevel'd script have no level.
level as varFramePtr->level - framePtr->framePtr->level, i.e. an uplevel-style relative level (>= 0) of the variable frame the command ran in. It is added only if that CallFrame is on the current callerVarPtr chain.
level is the uplevel-style relative level (0 or positive) of the variable frame the command ran in, so uplevel $level gives its context. eval/source frames share their caller's level. Proposed doc wording for info.n (9.x currently says "to be determined").
3588809fff.patch: VERIFIED
namespace unknown -> ::unknown in the global namespace, {} in a new namespace; after namespace unknown foo; namespace unknown {} -> {} again (main and 8.6). Doc says the default is ::unknown for all namespaces.
DOCS (still wrong on main; behaviour is as the reporter says on main, 9.0, 8.6, 8.5)
3547034fff.patch: VERIFIED
groff -man -Tutf8 doc/Object.3 renders the new paragraph correctly
DOCS (main, 9.0, 8.6 man pages say nothing about shared values)
DOCS (RFE-like improvement request; not checkable offline)
3376407fff.patch: VERIFIED
/* Number of bytes in token. */, and tclParse.c sets sizes as src - tokenPtr->start (byte pointers).
DOCS (still says "characters" on main)
Tcl_Size size; /* Number of bytes in token. */ and the parser computes sizes as byte offsets
3082225fff.patch: VERIFIED
clock scan 10/12/2010 -timezone :UTC -> 1286841600 (no error), clock scan 10/12/2010 -locale fr -> legacy [clock scan] does not support -locale
DOCS (the doc is wrong on main, 9.0, 8.6, 8.5; the code accepts and uses -timezone)
clock scan 10/12/2010 -timezone CST5CDT gives 1286856000 and -timezone :UTC gives 1286841600; -locale de gives "legacy [clock scan] does not support -locale"
3056056fff.patch: VERIFIED
command. work-a3/v3056.tcl on main and 8.6.18 confirms every statement in the new text: a caught tailcall gives code 2 and the proc still returns x; a second caught tailcall wins (y); catch {tailcall} cancels the pending one (the proc returns end); try ... on return catches it too; a bare tailcall returns "".
DOCS
catch {tailcall list x} returns 2 and the proc still returns x at its end; a second caught tailcall replaces the first; tailcall with no args is accepted (synopsis says command is required) and cancels a pending tailcall. tailcall.test now has 40 tests incl. catch cases (tailcall-12.x), and the related tickets are about behaviour already covered.
?command?, one paragraph).
DOCS (not checkable offline)
== != in the precedence table (OK there).
==/!=; the tutorial's operator list in Lesson 6 should too.
DOCS (claim confirmed; current tutorial text not checkable offline)
{([0-9])*\.?([0-9]*)} on 87.65 gives first=7; {([0-9]*)...} gives 87. {"([^"])*"} gives u, {"([^"]*)"} gives tavu.
([0-9])*, ([^"])*).
([0-9])* captures only the last digit; Tcl20a should use ([0-9]*) and "([^"]*)".
DOCS (not checkable offline)
DOCS (patch attached; not checkable offline)
puts "Directories: / "Files: in Tcl25.html (real syntax errors) and replaces chan copy/chan close by fcopy/close in Tcl26a.html (8.4 compat; unnecessary for 8.5+). Lesson 40 echo server issues (no -blocking 0, gets<0 treated as EOF) are real Tcl pitfalls.
DOCS (still valid upstream)
Status now: Open
doc-chan-push-result, not merged: Fix 7b0e690b70 and [2920003]: document that [chan push] returns the name of the channel, and that the handle passed to the transformation handler is not that DOCS (behaviour confirmed: [chan push] returns the channel name, the handler gets a separate rtN handle, on main, 9.0.5, 8.6.18)
init handle=rt0, push returns=file5.
DOCS (RFE: retitle introspection lessons, add event loop lesson)
DOCS (reported fixed in the tutorial source by tallniel 2009-12-23; website update status not checkable offline)
DOCS (RFE: lessons on TclOO, TDBC, coroutines, lambdas, ...)
DOCS (not checkable offline)
2561267fff.patch: VERIFIED (after the amendment; the original text was inaccurate for unicode-only values)
teststringobj set 1 "中文字"; teststringobj setlength 1 2 -> a 2-byte invalid string (ä¸ when shown as utf-8), so mid-character truncation happens as the ticket says. But teststringobj newunicode 1 0x4e2d 0x6587 0x5b57; teststringobj setlength 1 2 -> 中文: for a value that has only the internal Unicode rep (bytes == NULL), Tcl_SetObjLength counts characters, not bytes (tclStringObj.c, the else branch).
DOCS (still true on main: Tcl_SetObjLength works on bytes, and doc/StringObj.3 does not warn about it)
2544760fff.patch: VERIFIED
interp exists (no argument) -> 1, while doc/interp.n:281 shows the synopsis interp exists path
man -l interp.n shows interp exists ?path?; troff warnings unchanged (1, pre-existing ^v register)
DOCS (behaviour is intended and documented. "If path is omitted, the invoking interpreter is used", and the wrong-args message says interp exists ?path?; only the man page synopsis says path is required)
interp exists returns 1; two arguments give wrong # args: should be "interp exists ?path?"
interp exists path does not match the description or the implementation.
interp exists ?path?). Removing the 0-argument form would be an incompatible change, which is TIP territory.
DOCS (claim confirmed; not checkable offline)
regexp {a\tb} "a\tb" -> 1, regexp {\x41} A -> 1 (the RE engine handles backslash escapes itself since 8.1, see doc/re_syntax.n).
.\" TODO: document TCL_EVAL_INVOKE and TCL_EVAL_NOERR., and NRE.3 refers to Tcl_EvalObjv for flags)2424616fff.patch: VERIFIED
.\" TODO: document TCL_EVAL_INVOKE and TCL_EVAL_NOERR.
groff -man -Tutf8 doc/Eval.3 renders both entries
DOCS (still undocumented; doc/Eval.3 has .\" TODO: document TCL_EVAL_INVOKE and TCL_EVAL_NOERR., and NRE.3 refers to Tcl_EvalObjv for flags)
DOCS (behaviour is correct per switch.n; whether the Tcl8.html example misleads not checkable offline)
$center is a literal pattern; reporter's result is expected.
2028793fff.patch: VERIFIED
namespace eval ns {interp alias {} foo {} list A; interp alias {} q::bar {} list B} -> ::foo created (not ::ns::foo), q::bar -> ::ns::q::bar, namespace ::ns::q auto-created (v4docs1.tcl). interp.n says nothing about it.
DOCS (behaviour unchanged in main and 8.6, still undocumented in interp.n)
foo goes to ::, test::foo goes to ::test::test::foo and creates ::test::test); also checked that a relative qualified name is resolved in the *source* interp's current namespace (namespace eval ns {interp alias c a::b {} list} creates ::a::b in child c). [proc] instead fails with "unknown namespace".
2013699fff.patch: VERIFIED
incr s 0 on the tip build: " 12 "→12, +0x1_0→16, -0d1_000→-1000, 0b101→5, 0o17→15, _1→error; matches GetInt.3
groff -man -Tutf8 doc/IntObj.3 renders the new sentence and SEE ALSO entry correctly
DOCS (still true on main: IntObj.3 says nothing about which strings are integers; the syntax is documented only in GetInt.3 and expr.n)
DOCS (claim confirmed; not checkable offline)
if "$$y != 1" with y={[exit]} fails with invalid character "$" and never calls exit; if "$y != 1" does call exit.
$$y, which does not demonstrate the double substitution.
"$$y != 1" only raises a syntax error; the example should use "$y != 1" to show [exit] being run.
1689385fff.patch: VERIFIED
teststringobj newunicode 1 0x3b1 0x3b2 0x3b3; teststringobj setlength 1 2; teststringobj get 1 -> αβ (length counted in characters; generic/tclStringObj.c Tcl_SetObjLength still has the bytes==NULL Unicode branch), while doc/StringObj.3 describes only the byte case
groff -man -Tutf8 doc/StringObj.3 renders the new paragraph correctly; text matches the code (SetStringFromAny first, so only pure-Unicode values take that branch)
DOCS (behaviour unchanged in main, 9.0, 8.6; doc/StringObj.3 still describes only the byte case)
teststringobj newunicode + setlength: on a 3-char pure-Unicode value setlength 2 gives 2 chars (4 UTF-8 bytes); setlength 4 on 1 char gives 4 chars. 8.6 has the same branch (code reading; its teststringobj lacks newunicode).
1670783fff.patch: VERIFIED
f value becomes FLT_MAX; tcltest 1670.tcl on the tip -> binary format f 1e39 scans back as Inf, -1e39 -> -Inf, Inf/-Inf/NaN round-trip, payload NaN -> NaN(20000000), -NaN, and expr {$x+1} -> cannot use non-numeric floating-point value "-NaN" ... (so the man page is wrong on main)
man -l doc/binary.n renders both paragraphs correctly and matches the tip's behaviour above
DOCS — and the man page is now wrong on main/9.0: binary.n still says a value that overflows single precision becomes FLT_MAX, but since 85ce4bf928 (48706a2425, 2022-11-05, 9.0 only) it becomes ±Inf. 8.6 behaves as documented (FLT_MAX, also for Inf).
1657421fff.patch: VERIFIED
script -qc "tcltest tr.tcl" with puts [fconfigure stdout -translation] -> bytes crlf\r\r\n on a pty; to a pipe lf. Behaviour as the triage described, still undocumented in chan.n
man -l doc/chan.n renders the new sentence ("... except for terminals and serial ports on Unix ... the default is auto crlf ...") correctly
DOCS (behaviour unchanged since 8.4 and deliberate: REPRODUCED on 8.4.20, 8.6.18, 9.0.5, main)
fconfigure stdout -translation is crlf on all versions and puts sends "\r\r\n" to the terminal (Tcl's CR plus the tty driver's ONLCR); stdin is auto. To a pipe/file stdout is lf.
-translation {auto crlf} for every channel of ttyChannelType. CRLF keeps output readable when a script puts the terminal into raw mode (exec stty raw), at the cost of a stray CR in cooked mode, which only non-terminal consumers (acme, script logs) show. doc/chan.n says Unix output defaults to lf and doesn't mention terminals.
stty raw idiom.
-translation {auto crlf} so output stays correct in raw mode; in cooked mode the extra CR is harmless on real terminals. Proposed: document it in chan.n (patch available) and close.
DOCS (patch attached 43416cfd48; not checkable offline whether already applied)
DOCS (not checkable offline)
" is special only at the start of a word)
" inside a word is literal.
DOCS (RFE: drop "101" from lesson titles)
DOCS (not checkable offline)
[info nameofexecutable] would make them runnable.
DOCS (RFE-like improvement request)
}else{ and a brace on the next line are common beginner errors)
}else{ and newline before {.
Status now: Closed (Fixed)
DOCS question answered by current docs (socket.n -async section since 8.6.1, chan.n puts buffering); but testing found a REPRODUCED regression (9.0, main; not 8.6, 8.7b1): closing a blocking socket -async while the connect is still pending loses the buffered data
puts of 1 MB before the connect finishes is buffered (no error, -connecting 1, chan pending output = 1000000) and a blocking puts+flush waits for the connect, on 8.6.18 and main. But set s [socket -async ...]; puts $s hello; close $s (or switching to blocking before close): 8.6.18 and 8.7b1 deliver the data; 9.0.5, 9.0 tip and main fail with "transport endpoint is not connected" and the server receives nothing (3/3 runs each).
1274918fff.patch: VERIFIED
namespace eval a {upvar #0 x y} makes ::a::y; unset a::y unsets ::x while the link stays (setting x again shows through a::y); qualified myVar in a proc (c::b::r, and b::s from a proc in ::c) lands in ::c::b; a missing parent namespace -> can't create "nosuch::z": parent namespace doesn't exist.
upvar 0 loc ::c::b::q -> "can't create namespace variable that refers to procedure variable"). It is optional to mention.
DOCS
namespace eval a {upvar #0 x y} creates namespace var ::a::y, unset a::y unsets ::x but the link stays; qualified myVar inside a proc creates a namespace variable; missing parent namespace is an error. Since 9.0 (TIP 278) relative qualified names resolve only relative to the current namespace, so the "madness" in the 2006-08-26 comment is gone in 9.x (both vars land in ::c::b), still present in 8.6.
clock scan -format)DOCS (RFE: mention clock scan -format)
clock scan ... -format in Lesson 41 would suffice.
1072603fff.patch: VERIFIED
grep -rn tcl_pkgPath win/*.c unix/*.c -> still set only in unix/tclUnixInit.c (TclpSetVariables); doc/msgcat.n and doc/pkgMkIndex.n still tell readers to install under $tcl_pkgPath without a Windows caveat (tclvars.n and tm.n are already correct)
groff -man -Tutf8 doc/pkgMkIndex.n / doc/msgcat.n render the new sentences correctly (only the usual man.macros warnings); no code touched, no test run
DOCS (partly addressed)
967565ffff.patch: VERIFIED
show to the parent) -> info level in parent: 1 (child frames not counted; by design); doc/info.n:271-276 still calls the argument number and says nothing about interps
number -> level; troff 0 warnings before/after
DOCS (behaviour by design: levels are per-interp, the same ones [uplevel]/[upvar] use)
DOCS (still true: tcl.h includes only <stdio.h>; FileSystem.3 names R_OK/W_OK/X_OK/F_OK and O_RDONLY etc. but not their headers). The Tcl_StatBuf part is mostly solved by the TIP 316 accessors (Tcl_GetModeFromStat etc.).
624919ffff.patch: VERIFIED (ported)
\fIfIobjPtr\fR typo in the Tcl_IsEmpty synopsis was dropped: 50013b575a (2026-10-18, merged to main via f813fc7729) already fixed it. The ARGUMENTS hunk is unchanged; now 8 changed lines.
DOCS — dkf's 2002 doc fix is in (bytes are TUTF-8, nulls as 0xC0 0x80), but the argument text in doc/StringObj.3 still says the bytes "may contain embedded null characters unless numChars is negative" (wrong argument name, and contradicts the next sentence)
\fIfIobjPtr\fR typo in the Tcl_IsEmpty synopsis
DOCS
219149ffff.patch: VERIFIED
exec cat <v4fifo & -> returned after 1504 ms; exec sh -c {cat <v4fifo} & -> returned after 0 ms (the documented workaround works).
DOCS (REPRODUCED on main, 9.0, 8.6; by design according to ferrieux, 2013)
exec mkfifo fifo; exec cat <fifo >@stdout & on main, 9.0.5, 8.6.18: exec never returns (an after 2000 timer cannot fire, killed by timeout). exec sh -c {cat <fifo} >@stdout & returns at once and works.
sh -c workaround; no test, docs only)
exec sh -c {cat <fifo} & as the workaround.
DOCS