I don't think it's a very good idea: we didn't actually break ABI, and we could load an older Scope and it would work. The only thing would be preventing from loading Scope with an older Geany, which could be achieved by the plugin depending on a 1.34 API. And there's only 1 known plugin suffering from the issue anyway, so I don't think a "solution" should be penalizing everybody. Anyway, my suggestion is not really useful in practice, because all it does is try and preventing using an older Geany with a newer Scope, but anybody with an older Scope would not be stopped, and anybody with a newer Geany wouldn't need it… so it only can help for latest version of either Scope or Geany. Bah.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/433#issuecomment-372073923
