[davidw]: It would be nice to see at least a simple example included for all Tcl man pages (or at the very least point to another page including an example).

Here is the current state of things:
----
'''Files with examples:'''
 after.n    continue.n    for.n      interp.n   lrepeat.n    read.n    split.n
 append.n   encoding.n    foreach.n  join.n     lreplace.n   regexp.n  subst.n
 array.n    error.n       format.n   lappend.n  lsearch.n    regsub.n  switch.n
 bgerror.n  exec.n        gets.n     lassign.n  lset.n       rename.n  time.n
 binary.n   exit.n        glob.n     lindex.n   lsort.n      return.n  uplevel.n
 break.n    expr.n        global.n   linsert.n  namespace.n  scan.n    upvar.n
 catch.n    fconfigure.n  http.n     list.n     open.n       seek.n    vwait.n
 clock.n    fcopy.n       if.n       llength.n  proc.n       set.n     while.n
 concat.n   fileevent.n   incr.n     lrange.n   puts.n       socket.n
'''Files without examples:''' 
 Tcl.n    eof.n       history.n  package.n     registry.n  tell.n     variable.n
 case.n   eval.n      info.n     packagens.n   safe.n      trace.n
 cd.n     fblocked.n  library.n  pid.n         source.n    unknown.n
 close.n  file.n      load.n     pkgMkIndex.n  string.n    unload.n
 dde.n    filename.n  memory.n   pwd.n         tcltest.n   unset.n
 dict.n   flush.n     msgcat.n   re_syntax.n   tclvars.n   update.n
----
These are automatically generated (script below).  Some of these do have examples, such as msgcat and tcltest.  Others sort of do, but a functional bit of code that runs and demonstrates the command is always welcome.

'''Exception List''': The list of files that really do have (good) examples: msgcat.n tcltest.n.

and the list of files that describe commands that are too simple to really need examples (or that have them elsewhere): cd.n close.n

The following files probably don't need an example: Tcl.n, case.n, filename.n, library.n, packagens.n, re_syntax.n, tclvars.n (and perhaps safe.n too)
----
Adding an example doesn't take much time, and lots are already available on the wiki.  All you have to do is submit a patch to sourceforge.  The man page markup looks like this:

 .SH "EXAMPLES"

 A time server:

 .CS
 proc Server { channel clientaddr clientport } {
     puts "Connection from $clientaddr registered"
     puts $channel [clock format [clock seconds]]
     close $channel
 }

 socket -server Server 9900
 vwait forever
 .CE


I used this code to check:

 package require fileutil
 package require struct

 foreach res [fileutil::grep ".SH.*EXAMPLE" [glob *.n]] {
     lappend examplefiles [lindex [split $res :] 0]
 }
 set examplefiles [lsort $examplefiles]

 set allfiles [lsort [glob *.n]]
 set noexamplefiles [lsort [struct::set difference $allfiles $examplefiles]]

 puts "Files with examples: $examplefiles"
 puts ""
 puts "Files without examples: $noexamplefiles"
----
[DKF]: Remember that some [Tk] docs need examples as well, though I'd tend to say not the widgets, as they're better demonstrated as part of the general [widget] demo.

----
[AM] What about Wiki pages that show a particular package in action? I mention it here because it seems a nice starting place for it ... For instance:
   * the http package is nicely illustrated with the page on the [wiki-reaper]
   * [A little Unicode editor] might serve as an illustration for dealing with Unicode 

[DKF]: I'm trying to keep examples ''very'' short.  Both of those pages are several times too long for my current limit.
----
[Category Documentation]