Thank you! That was just what I was looking for.
--
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/1873#issuecomment-396490890
Closed #1873.
--
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/1873#event-1675554215
Geany version: 1.33
[gist: geany-bugs.txt
](https://gist.github.com/Tzqt/c5b34569bfb65aafeb5a8ade6bd1b7cd)
--
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/1876
It's partly interesting, but as every static analyzer it's at least half wrong,
so it has to be used carefully, and it takes time. For example, the first
issue is both irrelevant and mostly wrong (it probably comes from the fact
`Assert` is defined conditionally as a non-aborting check, which m
@LarsGit223 pushed 1 commit.
2f3f2cf utils: fixed build checks for VTE compatibility code
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany-plugins/pull/750/files/83a0cdcb4f3d4ca8de5908f710cc9bac51e7f708..2f3f2cff00ebaf2f44da
Note, individual pull requests fixing an individual fault or a very small
number (after showing it really is a fault, not just "because the analyser says
so") are likely to be welcome. Omnibus pull requests are likely to take a long
time to be accepted due to the issues @b4n notes above.
--
Y
