[Geany-Devel] Storing per-project settings for plugins
techet at xxxxx
Wed Feb 15 19:42:46 UTC 2017
there should be no problem with your approach (the extra content of the
config file will be preserved by Geany).
However, Geany offers plugins the possibility to read/write from/to the
project config files natively. When you register for the "project-open"
signal, the callback is invoked every time a project is opened and you
receive GKeyFile * config as a parameter from which you can read the
Similarly, when you register for "project-save", you can write your
configuration to the GKeyFile signal parameter. You can also force the
emission of the "project-save" signal by calling project_write_config().
You can check my projectorganizer plugin to see how to use the signals (the
signals are registered in prjorg-main.c). You can also check
On Wed, Feb 15, 2017 at 4:21 PM, Vasiliy Faronov <vfaronov at gmail.com> wrote:
> I have a small Geany plugin that needs some settings per Geany project.
> Currently, I do it as follows: the user manually writes a special
> section in the .geany project file, which my plugin reads as a generic
> INI file.
> I really like this approach (as a user) because it keeps all Geany
> project-related settings in one file.
> But is this approach OK in the eyes of Geany core?
> Devel mailing list
> Devel at lists.geany.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel