| command.compile.filepattern command.compile.subsystem.filepattern command.build.filepattern command.build.subsystem.filepattern command.build.directory.filepattern command.go.filepattern command.go.subsystem.filepattern | These settings choose which commands to execute when the Compile, Build or Go menu items are selected. The subsystem options determine for Windows whether the tools are run as command line(0), windowed(1), through ShellExecute(2), or through the director interface(3). When source files are in a different directory to that they should be built in, the command.build.directory property can be set to change to a particular directory before performing the build. |
| command.go.needs.filepattern command.go.needs.subsystem.filepattern | Sometimes a file must be compiled or built before it can be run. If this is the case, this setting indicates what command needs to be run to perform the compile or build step before running the file. When a file is compiled, this is noted and future runs will not perform a compile or build. To make a 'compile and go' Go command for .c files: command.go.*.c=$(FileName) command.go.needs.*.c=g++ $(FileNameExt) -o $(FileName) |
| command.name.number.filepattern command.number.filepattern command.is.filter.number.filepattern command.subsystem.number.filepattern command.input.number.filepattern | Extra commands can be added to the Tools menu. For example to include the 'astyle' indenter, the properties file could contain command.name.0.*.cc=Indent command.0.*.cc=astyle -taO $(FileNameExt) command.is.filter.0.*.cc=1 The first line defines the string that will appear in the Tools menu (immediately below 'Go'. The second line is the command string, similar to those of the compile, build, and go commands. The optional command.is.filter property states that the command modifies the current file so it may need to be read in after performing the command if load.on.activate is set. The subsystem determines how the command is executed on Windows. 0, the default is for command line programs, 1 for programs which create their own windows, 2 for running by using ShellExecute, 3 for running in an internal extension or director extension, 4 for running HtmlHelp on Windows, and 5 for running WinHelp on Windows. When using subsystem 4 or 5, the command has two parts separated by ! with the first part being the topic to search for and the second the name of the help file. On Windows, the optional command.input property specifies text that will be piped to the command. This may reference other properties; for example, command.input.0.*.cc=$(CurrentSelection) would pipe the current selection to the command processes. The command.input property is only supported for subsystem 0 (command line programs). If the text of a command starts with '*' then the Parameters dialog is displayed to prompt for parameters before executing the command. The initial '*' is not included in the command that is executed. |
| command.help.filepattern command.help.subsystem.filepattern | Defines a command to be executed when the help command is invoked or F1 pressed. On Windows, this often uses subsystem 4 as described above. On Linux, running man or a browser are common ways of displaying help. The word at the cursor is copied to $(CurrentWord) and this is often a good argument to the help application. The subsystem property works in the same way as for other commands. |
| command.scite.help command.scite.help.subsystem | Defines a command to be executed for help on the SciTE program itself which normally means displaying this file in a browser. |
т.к. кроме меня здесь никто не бывает. Да и во всём ру-нете ничего найти не возможно 
