Lugaru's Epsilon
Programmer's
Editor

Context:
Epsilon User's Manual and Reference
   Commands by Topic
      . . .
      Simple Customizing
         Bindings
         Brief Emulation
         CUA Keyboard
         . . .
         Command Files
      Advanced Topics
         Changing Commands with EEL
         Updating from an Old Version
            Updating from Epsilon 7
            Updating from Epsilon 4
         Keys and their Representation
         Customizing the Mouse
      Miscellaneous

Previous   Up    Next
Changing Commands with EEL  Commands by Topic   Updating from Epsilon 7


Epsilon User's Manual and Reference > Commands by Topic > Advanced Topics >

Updating from an Old Version

When you update to a new release of Epsilon, you'll probably want to incorporate any customizations you've made into the new version. You can save customizations in two ways: in a customization file called einit.ecm (see Command Files) (a simple text file which this version and future versions of Epsilon can read), or in a state file (a binary file that's specific to a particular major release). Prior to version 12, Epsilon only supported the latter method.

If you're updating from Epsilon 12 or later, and you saved your customizations in an einit.ecm file, not a state file, the new version of Epsilon should automatically use your customizations. You might have to modify some if they're affected by changes in the new version of Epsilon; read the release notes to see.

Otherwise, if you're updating from the Windows or Unix version of Epsilon version 8 or later, run the import-customizations command in your new version. This will transfer your customizations from your previous version and into your einit.ecm file for use in your new version. It works by running your previous version of Epsilon in a special way.

Once you've done that, future versions will automatically use your customizations. If you make more customizations, and choose to save them in a state file, not an einit.ecm file, you can use the list-customizations command to copy your current customizations to an einit.ecm file.

The next section explains how to update from an older version where import-customizations isn't supported.

One exception to the above is if you've customized Epsilon by writing Epsilon extensions in Epsilon's extension language, EEL. The list-customizations and import-customizations commands will help you insert references to your EEL source code files into your einit.ecm file, but it's possible that some of the built-in functions or subroutines called by your EEL source code files have changed. In that case, you will have to modify your commands to take this into account. See Changes from Older Versions for information on EEL changes.

Subtopics:

Updating from Epsilon 7.0 or Older Versions
Updating from Epsilon 4.0 or Older Versions



Previous   Up    Next
Changing Commands with EEL  Commands by Topic   Updating from Epsilon 7


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