.mb and .err files... ¡Viva MapBasic!
If you're wanting a regular expression to parse the error lines, this should do the trick.
^\({#0:p}\:{#1:d#}\):b{#3?#}$
This is a SlickEdit syntax regex, and I used the same {#} grouping numbers that is used by the next-error regex logic. Can MapBasic spit out compiler errors to stdout, or is it still limited to using the .err files? Go to Build | Configure Error Parsing, add this expression as "MapBasic". (If you're using v11.0 or v11.0.1, that is)
Anyway, if you want to open up the .err files after a build is complete, you can use this as a post-build step.
"%(VSLICKBIN)\vs.exe" "%rw*.err"
That just opens up any .err files right in the same instance of SlickEdit. Of course you'll need to tweak the "%rw*.err" part if your error output is going in some subdirectory.
But I wouldn't do it that way, since you have no support for using the next-error commands to jump to the offending error lines. And that's why you went through the trouble to put in a new error parsing expression.
Try this: Add the following as your post-build step
type "%rw*.err"
The
type command works like the
cat command, except that it will also place the file names right before the content if your *.err wildcard yields multiple files. This gets the contents of the .err files into the build output window, and it can be picked up by our build output error and warning scanning. (Of course you do need to add that MapBasic regex for those lines from .err files to be recognized as such)