> Also, TM is no fallback. It's simply what we've got to manage our tags.
I meant after filetype-plugins providing proper per-language support are implemented, TM would be the fallback. > In my opinion we should open it up more, in order to allow plugins to easily > get involved in tag management. Then when it gets supplanted/replaced/upgraded, any plugin using it breaks, not good. > In fact, plugins shouldn't disable TM to do their own stuff. This will only > cause pain since neither Geany itself or other active plugins can function > properly in such a situation. Instead, all plugins should cooperatively work > on the same tag management system (using proper APIs). I agree, but I don't think TM is the right API at present for this purpose. I'm just worried we're boxing ourselves in a corner if we expose a lot of the API and then need to make massive sweeping changes to it in order to accommodate useful APIs for plugins to provide these kinds of features. > Besides, peasy is not python specific, it doesn't even use any pygobject APIs > or has the necessary build system support for python-specific extension > modules. I meant your Python plugin should provide the extension module, not the proxy plugin loader. -- 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/pull/1187#issuecomment-242586152
