https://bugs.kde.org/show_bug.cgi?id=451238
--- Comment #8 from Lothar <loh....@googlemail.com> --- > The .kateconfig format predates the .kateproject and provides only mode line > level configuration for the editor component. > I don't see how mixing other configs into that file will help. Yes, it's off topic, but one last note/try. The build plugin is stand alone, and so it should be ok that in can be configured on its own. This file which "provides only mode line level configuration" is called .kateconfig so why not put more stuff there? I don't like to suggest to use the same JASON format, that would be odd. Based on https://docs.kde.org/stable5/en/kate/katepart/config-variables.html it could looks like this with the given example: kate-plugin-build-Kate-directory: build kate-plugin-build-Kate-build: make all kate-plugin-build-Kate-clean: make clean kate-plugin-build-Kate-install: make install In general <PluginId>-<PluginCustomKeyAndOrData> With <PluginId>=kate-plugin-build Kate=TargetGroup directory=Directory build=TargetName(1) clean=TargetName(2) install=TargetName(3) :foo=Data It would be nice, when in case of such a config is present, the plugin would suppress it's default target group. It's always irritating. -- You are receiving this mail because: You are watching all bug changes.
