@elextr commented on this pull request.
- the list and executes the @c _perform() function of the first extension in
+ * the list whose @c _provided() function returns @c TRUE. + * + * This function is typically called in the plugin @c init() function. + * + * Plugins wishing to re-register themselves, e.g. with a different priority, + * should first unregister themselves using @c plugin_extension_unregister() + * and call @c plugin_extension_register() afterwards. + * + * @param extension The @c PluginExtension structure instance provided by the + * plugin. + * @param ext_name Human-readable name of the extension that can appear in + * the user interface. The string should be reasonably unique so extensions can + * be distinguished from each other. + * @param priority The higher number, the earlier in the extension list the + * plugin is and the higher chance it becomes called when multiple extensions
and @elextr plugins priority == INT_MAX [end humility] :stuck_out_tongue_winking_eye:
For now lets see how well that advice works (or not).