My thoughts are that the context menu is for _commonly_ used _context dependent_ things, all current context menu actions relate to the current line, paragraph or selection. The proposed actions, relate to the current document, which is not really context dependent, and I'm not sure how commonly used they would be either (for me almost never). So I would say that, although the actions are useful, they are not suitable for the context menu.
I suggest these actions be located in a more appropriate place, and being file related, the `File` menu or maybe the `Document` menu comes to mind if the actions are built in to Geany. I have no strong opinion if these actions should be in a plugin or core given the small size, but I do want to address two things @SavSanta has said: 1. Plugin capabilities are pretty difficult to discover and remember. Agreed, but I'm not sure what a good solution for this is, other than a few "core" plugins, plugins are made by individuals and as such their documentation quality varies. Even if a capability is documented regular contributors don't necessarily remember them unless they use the capability themselves, let alone casual users finding it. So we don't always point others to existing plugin capabilities (as happened here). 2. Plugin actions go in `Tools`. That is a good solution, that way the user knows where to look, rather than the plugin spamming extra entries through other menus in unknown places (and when multiple plugins add to the same menu it grows uncontrollably). Whichever decision is made, one thing that should probably be done is to compare the implementation here to the implementation in the `Add-ons` plugin, because the plugin one has at least been tested in the real world for some years and has no issues that I can find. -- 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/2550#issuecomment-660622750
