https://bugs.kde.org/show_bug.cgi?id=365813
--- Comment #1 from Michael Pyne <mp...@kde.org> --- Created attachment 100253 --> https://bugs.kde.org/attachment.cgi?id=100253&action=edit Patch options matching named module-sets into module options The attached patch does what you want in my testing. I'm not sure if this simple change is exactly the best way to go though. Having a separate module-set-options seems needlessly user-hostile (though in fairness it is consistent with the way option handling has evolved in the code). It wouldn't be hard to adjust the config file parser to warn (or throw error) if a module-set and module both have the same name, and that would ensure that a plain 'options' block works for both..... except that 'options' is also meant to work in the case of modules that are not known about in the rc-file parser, but only become visible later (e.g. if you name a module-set 'juk' but perform a 'use-modules kde/kdemultimedia' in a separate module-set, you'd have two entities named "juk" that could have options applied). That's somewhat contrived of course, I'm just worried that "options foo ... end options" could end up meaning 2 separate things depending only on events that happen at runtime. With all that said, this does seem to work and they say that the perfect is the enemy of the good, so maybe it's best to integrate it and wait for problems (if any) before worrying too much? -- You are receiving this mail because: You are watching all bug changes.
