If in the build settings a compiler error regular expression is defined, both that expression as well as the default behaviour is used to identify error file name and line number in compiler output lines. This lead for e. g. the following output from a gcc
In file included from /home/torsten/projects/bar/bar/common/configvalues.c:33:0: /home/torsten/projects/bar/bar/common/configvalues.h:676:2: warning: #warning obsolete [-Wcpp] to 2 errors resp. warnings in the message window, but only the second line is a warning. I identified the problem is probably in the function msgwindow.c: msgwin_parse_compiler_error_line() where filetypes_parse_error_message() is called. If it returns FALSE the default way to identifier compiler error/warning messages without the regular expression is called. This is even the case when the user regular expression is valid, but does not match to a particular line. Short: the function filetypes_parse_error_message() should return TRUE, too if the regular expression does not match resp. the called function g_regex_match() return FALSE. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2817
