# HG changeset patch
# User Atul Varma <varmaa@toolness.com>
# Date 1211100463 25200
# Node ID 141cd4e612bbffd7aa7121c82092407eeb0b160e
# Parent  9767abfe290ba5527c6a6ff77f619200e4a77d2a
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.

diff -r 9767abfe290b -r 141cd4e612bb Makefile
--- a/Makefile	Sun May 18 00:44:02 2008 -0700
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,2 +0,0 @@
-all:
-	cp ${HOME}/.ensocommands my-enso-commands.py
diff -r 9767abfe290b -r 141cd4e612bb README
--- 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")