There are quite a few Issues/Pull Requests on Github about adding more
extensions to `filetype_extensions.conf` so various types of files are
detected/colourized/symbolized properly out of the box.
IMO, we need a policy/guidance on what is acceptable. The way I see it
there are a few ways we could handle it:
1) Add all filetype extensions possible as long as there's proof
somewhere they actually exist/are used.
2) Add only popular, generic ones, for example JSON or YAML or actual
programming languages supported by Geany.
3) Don't add anymore except when adding entirely new filetype support;
the `filetype_extensions.conf` file is user-editable precisely for this
I don't really have an opinion on this, but it would be helpful to have
some kind of consensus/policy on it, for the purposes of triaging Issues
and Pull Requests on Github.
I would like to start actions in geany from inside a geany plugin?
E.g. start the Color Chooser as if it was selected from the geany tools
I tried to call the callback function directly but that gives an linker
error for geany plugins (just logical).
Can I fire/send an event/message to make it being started? How do I do that?
We are happy to announce a new release of Geany!
For a comprehensive list of changes please see
* Improve snippet support (visual indicators and more, Thomas Martitz).
* Improve CLI argument help.
* Add "Close Documents to the Right" feature.
* Minor accessibility improvements.
* Fix crash if plugin manager is opened more than once.
* Update Python, Assembler and PHP filetypes.
* Updated translations: ca, de, el, es, fr, it, lt, lv, nl, pt, ru,
sk, sv, zh_CN
We want to thank all developers, translators and everyone who
contributed to this release with patches, feedback, bug reports and
so on. Thank you!
As usual, all downloads can be found on