<p>In <a href="https://github.com/geany/geany/pull/1038#discussion_r64387658">src/geanyobject.c</a>:</p>
<pre style='color:#555'>> @@ -380,3 +389,13 @@ GObject *geany_object_new(void)
>  {
>    return g_object_new(GEANY_OBJECT_TYPE, NULL);
>  }
> +
> +/** Get the global GeanyObject instance
> + *
> + * @return @transfer{none} The instance
> + */
> +GEANY_API_SYMBOL
> +GObject *geany_object_get_instance(void)
</pre>
<p>Nope, I thought about this too. But pygobject's magic (that allows passing callbacks that fit to the signal's expected signature) only triggers for GObject.connect(). For all other functions the python function must match the signature of the C callback, but for signal handlers there is only GCallback regardless of the actual expected callback. <code>plugin_signal_connect_full</code> wouldn't help.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly or <a href="https://github.com/geany/geany/pull/1038/files/df4e17e853e84a23f4fe27ba9bca0a614460b103..bdd0720128df6afda95851dd529baffa689431f5#r64387658">view it on GitHub</a><img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ32U91VMGtC-2qdoc9QeMaDkZTnmks5qEvnNgaJpZM4Ifw_7.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/pull/1038/files/df4e17e853e84a23f4fe27ba9bca0a614460b103..bdd0720128df6afda95851dd529baffa689431f5#r64387658"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>