Mercurial > my-enso-commands

comparison 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
comparison
equal deleted inserted replaced
3:9767abfe290b 4:141cd4e612bb
1 These are Atul's Enso commands. At present, the primary way to "install" 1 These are Atul's Enso commands. To install these commands, just add
2 these commands is by taking whatever commands you want (or, 2 the following line to your .ensocommands file (creating it if it
3 alternatively, the entire file) and putting them in the .ensocommands 3 doesn't exist) in your home directory:
4 file (creating it if it doesn't exist) in your home directory. 4
5 execfile("/absolute/path/to/my-enso-commands.py")