Why is a disk check on tab switch only done if the switch is from the tab menu, not clicking the tab? Surely it would be better for it to happen every tab switch so the file changed infobar comes up immediately on switch?
--
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/2861
… or user specific regular expression only
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2858
-- Commit Summary --
* added default checkbox to use built-in compiler output parse function or user specific regular expression only
-- File Changes --
M src/build.c (144)
M src/build.h (8)
M src/filetypes.c (24)
M src/filetypes.h (10)
M src/filetypesprivate.h (2)
M src/msgwindow.c (3)
-- Patch Links --
https://github.com/geany/geany/pull/2858.patchhttps://github.com/geany/geany/pull/2858.diff
--
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/pull/2858
When I reboot the system - geany loses the list of open files, how to fix it?
System Kubuntu 12, and 14, and 16 - The same behavior.
--
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/1826
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