Lugaru's Epsilon Programmer's Editor 14.00
Context:
|
Epsilon User's Manual and Reference > Commands by Topic > Simple Customizing > Command FilesA 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 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 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 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:
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:
Subtopics:
Command File Syntax
|