CTags KTE Plugin (was Re: Using KTextEditor plugins?)

René J.V. Bertin rjvbertin at gmail.com
Tue Nov 14 16:36:09 UTC 2017

Reviving this old thread.

Back in Februari I started looking into what's missing from KTextEditor plugin support but didn't get very far.

What's clearly missing is support for the configure scheme of those plugins; I already noticed that back then but as far as I can tell I never got an answer to the mail below.

That was never a big deal for the plugin I worked on at the time (zealsearch, for sending search terms to the Zeal docset documentation browser). That plugin either uses a single configuration file that's shared beyond hosts or I configured it to work with a default configuration. That's not an option with the CTags plugin, of course.

Kate offers 2 paths to its plugins' config. pages: via the global settings dialog and via directly via the toolbar buttons.

Which would be the best approach to follow in KDevelop ("best" being some combination of most robust, most elegant and easiest)? Entries for individual KTE plugins directly in the global settings panel, or grouped under the Editor section? None of the usual toolbar buttons appear to have a "Configure" entry in their menu so apparently that would not be the way to go?


On Monday February 06 2017 10:53:04 René J.V. Bertin wrote:
>On Monday February 6 2017 09:57:26 Milian Wolff wrote:
>>We potentially not support all that's needed. Please debug yourself by going 
>>through the ktexteditor integration in kdevplatform/shell to see if anything 
>>is missing.
>I did and indeed couldn't find anything suggesting that there is support for configuration dialogs in the code. I think if there were there would be a wrapper or emulation of KTextEditor::ConfigPage, correct?
>It doesn't really surprise me if Kate's snippet plugin is still the only officially supported KTextEditor plugin; it has no configuration dialog as far as I can tell.

More information about the KDevelop-devel mailing list