Running Epsilon via a ShortcutEpsilon comes with a program, sendeps.exe, that's installed in the directory containing Epsilon's main executable. It provides some flexibility when you create a desktop icon for Epsilon, or use the Send To feature (both of which involve creating a Windows shortcut).
If you create a desktop shortcut for Epsilon, or use the Send To feature in Windows, have it refer to this sendeps.exe program instead of Epsilon's main executable. Sendeps will start Epsilon if necessary, or locate an existing copy of Epsilon, and load the files named on its command line.
This is useful because Windows ignores a shortcut's flags (command line settings) when you drop a document on a shortcut, or when you use the Send To feature. (If it used the flags, you could simply create a shortcut to Epsilon's main executable and pass its -add flag. Since it doesn't, sending a file requires a separate program.) Also, Windows sends long file names without quoting them in these cases, which would cause problems if sent directly to Epsilon.
Sendeps may be configured through entries in a lugeps.ini file located in your Windows directory. It will use a lugeps.ini in the directory containing sendeps.exe in preference to one in the Windows directory. The section name it uses is the same as the base name of its executable (so making copies of the executable under different names lets you have multiple Send To entries that behave differently, for instance).
These are its default settings:
Normally relative file names on the sendeps command line are sent to Epsilon as-is, along with a -dir flag indicating Sendeps's current directory. Set senddir to zero and Sendeps will convert each file name to absolute form itself and omit -dir.
You can tell Sendeps to use DDE instead of its usual -add
protocol by setting usedde to
When you invoke Sendeps without specifying a file name on its command
line, its behavior is controlled by the