With this revision, should the details about adding commands be changed so that they reflect the fact .ensocommands is a folder (if I understood the patch :S)

From the homepage at google code:

Creating, running, and modifying Enso commands is intended to be as easy as possible. To create a command, simply create an .ensocommands file in your home directory if it doesn't already exist (if you're on Windows, this directory is pointed to by the HOME environment variable). This file is just a Python script containing classes and functions representing available commands. 

doh! Shame you can't unwrite things - sorry about earlier comment. After actually reading the post about the patch I see that it doesn't make .ensocommands a folder but uses a different folder. Sorry! Though it'd still be nice to add the new details to the frontpage :)

Aha. I didn't update the front page because I'm not changing the core Enso trunk; I'm changing the community branch. Some documentation on the community branch would be no bad thing, but I'd like to wait until we have installation of Enso plugins from the web sorted and in the community branch. At that point I shall make a big play for making the documentation apply to the community branch rather than the untouched trunk, especially since the Humanoids are all about Ubiquity anyway ;-)