Thank you.

I would prefer not to correct the manual, but to change line 1114 resp. the called match function filetypes_parse_error_message to give the regular expression the only priority - if it is defined and valid. Then both use cases are covered: a) use the default implementation to match as much lines as possible and b) use the user defined regular expression to match only those lines which match the expression. This would make it IMHO more clear to the user in the build dialog settings,too, that the regular expression is responsible for finding compiler error messages or warnings when someone define one.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.