Current codebase has a lot of if branches checking for specific languages, approaching an implementation of this design would likely mean that those hard-coded checks would want to move to plugin-based approach; that is to be recognized as some work.

Additionally to what can be found by looking at the aforementioned checks, we could look at how language-specific plugins have been designed&implemented in other notable editors.

Finally, the design should not be too broad to conflict with the "Lite" nature of Geany, and that is surely a challenge as well.

I recognize the problem with callbacks and asynchronous replies, and I can foresee a situation where Geany gets "stuck" because of plugins (so extra debugging/development features are probably needed to accommodate for the variability introduced by such plugins). You can probably already see some of these problems with "custom actions". I have no simple solution for this either.

What do we do with the mentioned issues/PRs? #1187 and #1195 look particularly relevant

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.