Show in Frame No Frame
Up Previous Next Title Page Index Contents Search

5.5 Command line operations

This section describes the ways to configure MetaEdit+ on startup by using command line parameters and operations. The Modeler version of MetaEdit+ supports only a small set of command line parameters. Command line parameter support for other more advanced operations is supplied in the API add-on – for more information about these parameters and operations see the Command line operations in Chapter 10 the ‘MetaEdit+ Workbench User’s Guide’.

The following table summarizes the command line parameters available in the Modeler version of MetaEdit+:
Sets the MetaEdit+ working directory to be the directory in the argument. Argument is a string representing a directory name, or a file name within a directory. The file or directory must exist. Cannot be used when logged in. When reading metaedit.ini from this new directory, only those settings explicitly mentioned in the ini file will be changed.
Imports the named program, type or model patch (.mep, met, .mec, .mxt, .mxs, .mxm). Note you must be logged in for all but .mep patches.
Imports .mep program patches. Patches are named in a patches.txt file in the current directory or patches subdirectory. If there is no patches.txt file, all .mep patches from the patches subdirectory are taken in alphabetical order.
All the commands have the same structure: the first parameter is a case-sensitive command name (with no - or / prefix). The command name shows how many arguments it expects according to the number of colons in the name: fileInPatches expects no arguments, fileInPatch: expects one argument, and currentDir: expects one argument. Note that for commands that expect arguments, there are no spaces in the command name, and the last character is always a colon.

After a command name expecting N arguments, the next N parameters on the command line will be used as those arguments. If a parameter contains a space, you will need to escape it or quote the parameter according to the rules of your platform.

As an example, consider the following command line that would file in the normal patches, file in an extra foo.mep patch file, and change the current directory to D:\
mep55.exe fileInPatches fileInPatch: foo.mep currentDir: D:\
Here, mep55.exe is the name of the MetaEdit+ program executable. The first parameter given to the executable is fileInPatches, which takes no arguments. The second parameter is fileInPatch: with its argument foo.mep. The third parameter, currentDir:, follows with its argument D:\.

Show in Frame No Frame
Up Previous Next Title Page Index Contents Search