You can find me on the chat quite often. I'm addicted to Tcl. Not many contributions to the wiki yet, but here are some I think are especially neat. * [Playing Scheme] * [Options and Arguments] * [Inspecting TclOO] * [Extending TclOO with metaclasses] * [Ensemble objects] and a few things I've put here for lack of a better home: * [Heronian triangles] * [IPv6 Addresses] .. other random ranty stuff: * [loop microbenchmark] * [TIP #431 Discussion] Soon, some of my essential code will appear on https://chiselapp.com/user/aspect/ ---- *** On Wiki *** **** Syntax summary? **** I keep screwing up wiki syntax. Is there an existing (concise) page with example formatting to use as a reference? Definition lists, which way around links go, indent levels for lists, how to do categories correctly, how multiple discussion tags work, those tabular summaries on project pages .. **** Content deletion **** There's a lot of old discussion in here that hasn't been relevant since last century. While preserving it for folks stuck on old versions and archaeology is desirable, wiki usability would be dramatically improved by a lot of this content disappearing, or moving to somewhere less distracting to readers and editors. I often get stuck, trying to contribute to a page in poor state and at the same time make its navigability better (or at least not worse!). Can the gnomes offer any hints or policy? [PYK] 2015-01-26: Lately I've found myself making links to previous versions of the page when I've decided to delete some old content but still leave a breadcrumb to it for anyone who might be interested. A single page can take horurs or days to reorganize, but when there isn't time for that, even the smalled incremental cleanup is a step in the right direction. **** Manual Content in the Wiki **** See for example [send]. Content above the discussion repeats the manual verbatim. This is a problem because changes to the manual don't make it into the wiki. Wiki content goes stale, people get misled, someone eventually has to change it by tediously copying text from the manual into wiki syntax. In the meantime, pointless content gets in the way of maintaining the good stuff. IMHO all verbatim manual content in the wiki '''should be erased'''. If you have an opinion on the matter, please write it here: [PYK] 2015-01-26: I think that the wiki page for a command should comprehensively describe the command, but if the description truly is verbatim, there's no harm in deleting it and pointing to the official documentation. I'm more likely to update and wordsmith verbatim documentation rather than delete it. **** Manual Links **** A lot of manual links go to `purl.org` or to specific versions of Tcl. More robust links can be generated that look like: http://www.tcl.tk/man/tcl/TclCmd/Tcl.htm I'm fixing them when I touch related pages, but a wiki macro would also help. ---- *** Random Blatherings *** ... this is where I will eventually elaborate my plans to promote [Abstract Interpretation], [Macro]logy and/or [inline]-able procedures to make Tcl more fun and performant. [RLE] (2014-01-26): Re. wiki syntax, does the [Formatting Rules] page not fit your requirements? <> Person