Here's one of those little things that irritate me about bash ,or more specifically its command line editing: its command historyis (sometimes) mutable. Under at least some circumstances, you canoverwrite a command that is in your history by going back to it (withsearch or cursor up) and editing it again. When you do this, the oldversion of the command is gone permanently; if you cursor back to itagain, you see your freshly edited version.

(This doesn't seem

There is one significant imperfection in my effort to give commentreaders as much context as possible : the 'AddComments' link itself is easily accessible without having read anycomments. The problem with this is that the people who are leavingcomments are exactly the people you most want to have all of thecontext.

The obvious thing to do is to only put the 'add comment' link on thebottom of the page that has all of the comments, so people have toat least scroll past the existing comments to

DWiki has a pretty simple way of displaying comments; all comments ona single page, which also has the main entry. There's a lot of moresophisticated comment handling systems, like LiveJournal and Slashdot,and I won't deny that part of why DWiki is simple is that simple is less code . But part of it is deliberate,because it's all about the context.

Specifically, I want people who read comments to have as much contextas possible, which means that I want them to