Mercurial > my-enso-commands
changeset 4:141cd4e612bb
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 | 9767abfe290b |
| children | 56d44190362e |
| files | Makefile README |
| diffstat | 2 files changed, 5 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- 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
--- 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")