UVviewsoft forums

• parses the text in the output window

• identifies file names, line and column numbers and the associated messages

• jumps to the file location in the editor and displays the message

• allows stepping forward and back through a list of all messages in the output window

* LOG_SET_REGEX: Sets parsing RegEx for log panel. Param "text" is RegEx string. RegEx must have some groups in round brackets, indexes of these groups must be passed in separate API calls. All lines in log panel, which can be parsed by this regex, will allow navigation to source code by click or double-click.
* LOG_SET_LINE_ID: Sets index of regex group for line-number. Param "text" is one-char string from "1" to "8", and "0" means "not used".
* LOG_SET_COL_ID: Sets index of regex group for column-number. Param "text" must be str(number).
* LOG_SET_NAME_ID: Sets index of regex group for file-name. Param "text" must be str(number).

        {   "run": "dart2js.bat",
            "re": "(?P<file>.+?):(?P<line>\\d+):(?P<col>\\d+): Error:.+",
            "name": "Dart"   

• The feature I was asking about already exists

• The one thing that steered me in the right direction was the statement about the 'external tools'

• I searched the .config directory and found cuda_exttools and in there 'readme.txt'. That helped decidedly more than the help provided when clicking the 'Help' button.

• This file had a hint about the configuration of the external tools plugin. This is the only place where I could find a little information about the meaning of the 'Capture output' and 'Pattern' fields in the tool configuration dialog.

• Setting the parsing pattern is not simple and I could not manage to implement it correctly. It's easy if you know how it works under the hood. If you don't you are pretty much lost.

• However, I found you can load a preset by clicking a button at the bottom of the dialog. And wouldn't you know, there are a whole bunch of parsers for different compilers already defined, including one for Java.

• So, I simply loaded that and it worked right away.

• The regex for that preset also showed me what I did wrong with my matching pattern. That might serve as a hint for others. If there is no preset for your compiler or tool, just load any preset and study the regex. In my case I needed to match single colons and had used ([:]) but it turns out it should be just the colon by itself (:). You also need to parse all the way to the end of the line, so it must be closed with (.+) which I had omitted. In hindsight it's obvious, but when you are working on it with no feedback what might be wrong it's really difficult.

• When the tool has run to completion, automatically start the parser and keep running it for every line of the output and build a list of all matches

• Provide a hotkey response. In my current editor it is shift+ctrl+down arrow for next and shift+ctrl+up arrow for previous

• This steps forward and reverse through the list and does two things: (1) it jumps to the corresponding text location in the editor, just like the double click and (2) it highlights the corresponding line in the Output Panel.

• click on the Tools menu

• once that has opened click on the Results entry

• another menu opens and you have to click on either Next tool result or Previous tool result