@codebrainz of course you can, but when @b4n agreed that extra changes 
unrelated to this PR are needed, I just noted they should be a separate 
issue/PR, not something that stalls this PR.

@kugel- this PR does not go on top of #1470 does it? The problem was just 
identified there and this can be applied separately?  And basically its got 
nothing to test, except warnings with `--b4n-pedantic` compile options?

-- 
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/1561#issuecomment-318229671

Reply via email to