Certain configuration files are executed automatically to set up the environment whenever MULTI starts up, and additional script files are executed whenever the Debugger starts on a particular program. MULTI parses these files in the following order (if a file does not exist, it is skipped):
Because changes to the same configuration item (see Chapter 10, "Configuration commands") can exist in multiple files, the execution order of such files is important. A configuration change can override the effects of a previous change.
The global config file, user config file, and command line config file are parsed on MULTI startup, whether the Builder comes up first or the Debugger. The global script file, user script file, and command line script file are executed once when MULTI's first Debugger window appears (the first time you start a Debugger on a program from an invocation of MULTI). The program script file is executed every time that program is loaded into a Debugger window, i.e., on every new Debugger window on that program, on every program reload (debug command with no arguments), but not on every program restart.
If you load a new program into an existing Debugger, MULTI will automatically execute the commands in the new program's script file (if any) but does not clean up the effects of the old program's script file (if any).
All Debugger windows launched in a debugging session share the same Debugger environment. If you launch multiple Debugger windows from the same MULTI program (for example, the Builder), all the script files of the corresponding debugged programs will be executed, resulting in the final Debugger environment.
$MULTI'S_INSTALLATION_DIR/config/multi.cfg
This file is useful in setting up a common environment, required by whole user groups when debugging any program. If you run the MULTI editor as a stand-alone executable (not from within MULTI(#) it uses me.cfg instead of multi.cfg.
This file is useful in setting up a common environment, required by a single user when debugging any program. If you run the MULTI editor as a standalone executable (as opposed to from within MULTI), it looks for me.cfg instead of multi.cfg.
You can specify a configuration file on the MULTI command line with -config filename or -configure filename. This feature is not available when running the MULTI editor as a separate executable.
$MULTI'S_INSTALLATION_DIR/config/multi.rc
This file is useful for commands which need to run once when any person in a whole user group starts the Debugger the first time in a debug session.
This file is useful for commands which need to run once when debugging any program by a single user.
You can specify a script file in the command to run MULTI with the -rc option, such as multi my_prog -rc your_script.
$EXECUTABLE_DIR/executable_name.rc