Mercurial > my-enso-commands

diff README @ 4:141cd4e612bb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
With the advent of the scriptotron's ability to auto-detect execfile() calls in .ensocommands, the procedure for installing my commands has changed, and I no longer need to have a makefile that copies my .ensocommands file into my-enso-commands.py. Modified the README to reflect this.
author Atul Varma <varmaa@toolness.com>
date Sun, 18 May 2008 01:47:43 -0700
parents 429e04abae50
children
line wrap: on
line diff
--- a/README	Sun May 18 00:44:02 2008 -0700
+++ b/README	Sun May 18 01:47:43 2008 -0700
@@ -1,4 +1,5 @@
-These are Atul's Enso commands.  At present, the primary way to "install"
-these commands is by taking whatever commands you want (or,
-alternatively, the entire file) and putting them in the .ensocommands
-file (creating it if it doesn't exist) in your home directory.
+These are Atul's Enso commands.  To install these commands, just add
+the following line to your .ensocommands file (creating it if it
+doesn't exist) in your home directory:
+
+  execfile("/absolute/path/to/my-enso-commands.py")