Lugaru's Epsilon
Programmer's
Editor

Context:
Epsilon User's Manual and Reference
   Commands by Topic
      . . .
      Repeating Commands
         Repeating a Single Command
         Keyboard Macros
      Simple Customizing
         . . .
         Variables
         Saving Customizations
         Command Files
            Command File Syntax
            Command File Examples
            Building Command Files
      Advanced Topics
         Changing Commands with EEL
         Updating from an Old Version
         Keys and their Representation
         Customizing the Mouse
      . . .

Previous   Up    Next
Saving Customizations  Commands by Topic   Command File Syntax


Epsilon User's Manual and Reference > Commands by Topic > Simple Customizing >

Command Files

A command file specifies macro definitions, key bindings, and other settings in a human-readable format, as described in the next section.

One important example of a command file is the einit.ecm file. Epsilon automatically loads this file each time you run it, immediately after loading its basic definitions from a state file.

The -noinit flag tells Epsilon not to load an einit.ecm file. You can also set the load-customizations variable (and save the setting in your state file) to turn off reading an einit.ecm file.

You can use the list-customizations command to add a list of all the customizations in the current session of Epsilon to the end of this file, commenting out any existing settings there.

Or you can set Epsilon to automatically record many types of customizations in this file. Set the record-customizations variable to 1 to tell Epsilon to record all such customizations, but not to automatically save them. Set it to 2 to record and save them without prompting.

With either method, you can always edit the customizations file to remove any settings you don't want, or use commands like insert-macro to add specific customizations to it.

Epsilon creates its einit.ecm file in your customization directory. Under Unix, this is ~/.epsilon. Under Windows, its location depends on the version of Windows, but is often \Documents and Settings\username\Application Data\Lugaru\Epsilon or \Users\username\AppData\Roaming\Lugaru\Epsilon. See The Customization Directory for details. Epsilon searches for an einit.ecm file using your EPSPATH. The edit-customizations command is a convenient way to locate and start editing this file.

If you prefer to write customizations in EEL format, you can create an EEL source file named einit.e in the same directory as your einit.ecm file, and tell Epsilon to load it at startup by adding this line to your einit.ecm file:

(load-eel-from-path "einit.e" 2)

You can use the load-file command to make Epsilon load the settings in any command file. It asks you for the name of a file, then executes the commands contained in it. The load-buffer command asks you for the name of a buffer, then executes the commands contained in that buffer.

Set the variable einit-file-name to make Epsilon look for a file with a name other than einit.ecm. For instance, by using the command line flag -d to set this variable, you can make a particular invocation of Epsilon load a specialized set of commands and settings to carry out a noninteractive batch editing task.

Standard bindings:

    edit-customizations
   load-file
   load-buffer
 

Subtopics:

Command File Syntax
Command File Examples
Building Command Files



Previous   Up    Next
Saving Customizations  Commands by Topic   Command File Syntax


Lugaru Copyright (C) 1984, 2012 Lugaru Software Ltd. All Rights Reserved.