I think <b>Geany</b> would look even better if the Java boxed types (Integer, Float Double etc) were highlighted just like the unboxed equivalents because this makes code so much easier to read: one of many reasons I like using <b>Geany</b> so much.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/734
For some reason the ./waf updatepo script doesn't work. It complains output missing a file. The reason seems to be that (recently?) the files in multiterm are changed from .c to .vala. Simply faking the system by setting a symbolic link for each .c file in this ./multiterm/src directory let the waf script run correctly, like:
ln -s ./multiterm/src/config.vala ./multiterm/src/config.c
But that's a workaround, not a permanent solution, I think.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/293
@b4n I guess that would be possible but I just can't imagine the situation where this would be needed. If someone installs the new geany version then the config files should be at the new locations (and if there's some problem e.g. during packaging then IMO it's better if things fail loudly and the package gets fixed instead of working around the problem in the code).
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/485#issuecomment-153797689
It may happen (and happens on OS X) that plugin activation using
plugin_new() triggers some action which causes the tree view to
update. However, as the old plugin was freed before, the tree view
contains an invalid pointer to p which causes invalid memory access.
After freeing the old pointer, set the tree view value to NULL - the
plugin pointer is checked at other places for NULL value so it
doesn't crash.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/732
-- Commit Summary --
* Avoid possible invalid memory access when activating plugin
-- File Changes --
M src/plugins.c (3)
-- Patch Links --
https://github.com/geany/geany/pull/732.patchhttps://github.com/geany/geany/pull/732.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/732