I’ve noticed that both pluginload and library_loaded are run prior to plugin types and queries being merged to the models (see beets.ui:_setup), so if a plugin has logic that depends on those, it has to postpone it until later on, rather than initializing it up front. Any thoughts on this? It’d be nice to either shift this order, or add a new “we’re fully set up” event.
Huh, you’re right that seems awfully strange. It seems like at least pluginload should run after the plugins are fully loaded, right? I would definitely support rethinking this.