@b4n, adding custom filetypes to the system directory is not "misbehaving", its just installing the filetype for all users of the machine :smile:
But if the administrator is smart enough to do that then they are smart enough to fix it after we move the files.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/485#issuecomment-154562146
(I thought I posted a comment about that, but looks like I forgot)
@techee I was thinking about a misbehaving user that would have put some custom filetypes in teh system directory. However, we could very well accept that just like changes to existing files would get overwritten, new files can get ignored.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/485#issuecomment-154503260
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