Help Topics

Options - User Tools

File extension tree

This tree represents function key assignment for each file type. It is possible to assign four function key commands (F9-F12). To add new execute key command file type, press Add button. In dialog, enter list of file extensions for which this command assignment will be used.


Enter command that will be executed. To quickly browse to the executable file, press "..." browse button. This box can contain path and name to the executable file. If other file type is specified, EditPlug will try to execute the associated application. Don't specify any command line parameters in this box.

Start in

Specify directory that will be used as default when executing command. If omitted, default directory will be directory where is editing file.


Place command line parameters here. %Macros can be used here and will be expanded.


Select window type in which command will be used. If executing application is console or DOS application and Capture console output option is checked, this parameter will be ignored.


Enter some text that will describe this command. This text will appear as Tools menu command caption and as hint on corresponding toolbar button.


Select save mode that will be used before command is executed.

Use short DOS names

If checked, all paths and file names will be converted to the old DOS 8.3 file name format. Check this option if you're executing DOS application that can't handle long file names.

Capture console output If checked, all output of the executed command will be redirected to the small window in the bottom instead in separate console window. You should be aware of following notes:
  1. If executed command enters infinite loop and you're using Windows NT or Windows 2000, Terminate button will be shown in console output window and executing command could be terminated.
  2. If you use Windows 9x/Me, Terminate function wouldn't be available and if application enters infinite loop, you should use task manager or some third party utility to terminate the process.
  3. If executed application needs user input, this will be NO indicated and application will probably look as locked.
Compiler output parser rule

See Parser Rule.

Optional generic runtime parameters

Runtime parameters can be used in any of above fields:

%n	file name with path
%f	file name only, without path
%F	file name only, without path and extension
%p	file path only
%e	file extension only
%s	value specified in "Start in" box
%P	file specific parameters - see below for more info
%l	current line number
%c	current column number
%w	word under cursor
%%	percent sign
%?	shows parameter input dialog to enter additional parameters
%S      editor selection
File specific parameters

Parameter %P is file specific parameter and it can be used for every edited file separately. In the first line of code following comment should be added:

// %PARAMETERS = "my additonal parameters"

Of course, replace '//' comment sequence with comment chars of language you use. You can use escape (\) character to enter quotes (\") or backslash (\\).

For example, if Parameters in Environment options dialog is defined as "%n %P blabla %e" and first line of code contains definition such as %PARAMETERS = "-first /second -\"third\"", your compiler (or whatever) will be started with following parameters:

mycompiler.exe c:\test\test.ext -first /second -"third" ext