WrapEarnPass created an issue (geany/geany#4609) In order to ensure that arbitrary commands in geany/geany-plugins#1577 behave similarly to Geany I wanted to ensure that I was matching the output from existing tools, like Build.
The magic that determines if a message is an error ```msgwin_parse_compiler_error_line``` is in a GEANY_PRIVATE declaration. So, I am unable to use the ostensibly standardized method. I can trigger the behavior by just coloring everything in compiler COLOR_RED, as the on_msgwin_button_press_event will call msgwin_goto_compiler_file_line which is gated to run msgwin_parse_compiler_error_line if the color is COLOR_RED I am unable to accurately reproduce the behavior without re-implementing the majority of msgwin_parse_compiler_error_line in my own code, bypassing the usefulness of the standardization of error handling and error_regex. It would be nice to expose some aspect of the error parsing publicly so that plugins can consume it. I would like to be able to call something like: ```gboolean output_contains_error(gchar* output, GeanyDocument*|GeanyFiletype* );``` to be able to utilize Geany's definition of "an error" from a geany-plugin. Workaround: I don't think that being forced to use COLOR_RED on everything is a reasonable workaround, but it is an option. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/4609 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/[email protected]>
