Tool Output Configuration

• Discard. Just ignore caught output. Nothing more.
• Send to Output Window. Text send to output by external tool is forwarded to default or custom output window.
• Replace selected text. Selection (selected text) in current document will be replaced by output of the tool (text caught). If nothing is selected output text inserted in current cursor position.
• Replace current document. Text in the current document will be replaced by output of the tool (text caught).
• Replace Clipboard content. Current content of the Windows Clipboard will be replaced by output of the tool (text caught).
• Insert before/after selection. The output of the tool (text caught) will be inserted before/after selected text (left/right border of selection). If nothing is selected for both cases cursor position is taken as anchor for selection.
• Show as Tooltip. Caught output text of the tool is shown in tooltip above current cursor position in document.
• Create a new document. New document is created and output of the external tool is forwarded there.

The following options are only available if selected Send to Output Window.

• Clear Output. Clear output window.
• Echo input. Do not delete input text (normally it will be duplicated by tool itself, but not by Ruby).
• Set Focus. Set focus to output window when tool is started. Useful if tool allows (and requires) input.
• Print execution data. Prints statistical data as “Started”, “Canceled”, “Elapsed” etc to output.

If you use not default output window, tool will have his own output window, marked by tool title. In this case, for better customizing of the presentation, you can select custom syntax for it and apply different font/color settings in compare to default output (white on black, fex). Best way to get custom settings for output is to copy output_spec.xml (do not forget to change id inside) to another file. Than you get additional syntax you can customize.

The pattern here defines, how HippoEDIT will behave if user double clicks on some line in output window. Pattern instructs the application how parse line been double clicked and what can be extracted from it. By design, if output contains some error information, that can be parsed, user should be able to navigate to document/line/position mentioned in message after double click on corresponding line.

Tells HippoEDIT to try all standard hardcoded patterns (can be seen in menu for regular expression field). Use it as default, and if does not work, than OK, you need to provide your own regular expression for parsing of the output.

If default output pattern does not work for you, you can provide your own. Use menu arrow right to field for examples.

For navigating, editor needs document path, line number inside the document and position in line. Configure which tagged expression matches to which parameter in Regular expression tags area. Only line parameter is obligatory. If no document found, editor will try to navigate to line is current document. If position is not defined, 0 position will be taken.

Here you can test how good your regular expression can parse test output. Define regular expression you think should work in fields above and paste in test output into field and press Check.

By default, or decoding current system code page (encoding) is used. But there is not an obvious way to define it also explicitly. Not in UI, but in xml file where tool is stored (usually *_user.xml, where * correspond to language id for which tool is defined, but can be also in project). You can set “encoding” attribute for tool. And only from 1.50.

<TOOLS>
    <Tool name="cmd" capture_output="true" command="cmd.exe" encoding="866"/>
</TOOLS>