[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     dict.n        format.n   list.n       regexp.n    time.n
 append.n    encoding.n    gets.n     llength.n    registry.n  trace.n
 array.n     error.n       glob.n     lrange.n     regsub.n    unset.n
 bgerror.n   exec.n        global.n   lrepeat.n    rename.n    uplevel.n
 binary.n    exit.n        http.n     lreplace.n   return.n    upvar.n
 break.n     expr.n        if.n       lsearch.n    scan.n      variable.n
 catch.n     fconfigure.n  incr.n     lset.n       seek.n      vwait.n
 cd.n        fcopy.n       interp.n   lsort.n      set.n       while.n
 clock.n     file.n        join.n     namespace.n  socket.n
 close.n     fileevent.n   lappend.n  open.n       split.n
 concat.n    flush.n       lassign.n  proc.n       string.n
 continue.n  for.n         lindex.n   puts.n       subst.n
 dde.n       foreach.n     linsert.n  read.n       switch.n
'''Files without examples:''' 
 Tcl.n   fblocked.n  library.n  package.n     pwd.n        tcltest.n  unload.n
 case.n  filename.n  load.n     packagens.n   re_syntax.n  tclvars.n  update.n
 eof.n   history.n   memory.n   pid.n         safe.n       tell.n
 eval.n  info.n      msgcat.n   pkgMkIndex.n  source.n     unknown.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]