https://bugs.kde.org/show_bug.cgi?id=468997
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Resolution|--- |DUPLICATE
Status|REPORTED |RESOLVED
--- Comment #1 from Nate Graham <n...@kde.org> ---
> This definitely falls under the category of "over-broad requests for giant
> changes to everything",
Indeed. :)
The issue here is that there's no single magic bullet solution. Every app and
also Plasma needs to be ported to save its state in its state file rather than
its config file. This has been happening slowly, and some apps like Dolphin do
it now, but in the end, every single app needs to be ported to do it. It can't
be done automatically because someone needs to make the judgment about what
counts as state and what counts as settings and handle them separately.
If you'd like to help out with this effort, it could be a good place to get
involved. It's not hard to do. Here are the two commits that did it for
Dolphin, for example:
-
https://invent.kde.org/system/dolphin/-/commit/946b911a5d340d7672db9802579f658aeba738b0
-
https://invent.kde.org/system/dolphin/-/commit/b497dc9cbd1236790b5267710f5fb8370253d005
Not too bad, right? It's basically a matter of replacing
"KSharedConfig::openConfig()" function calls with
"KSharedConfig::openStateConfig()" for data that should be considered
semi-volatile state, not user settings. So maybe you can help by making similar
changes for apps where you encounter this problem.
If not, then it would be useful if you could submit a bug report for each
individual app that exhibits this problem, and then add it to the "see also"
list in Bug 397602.
> A temporary fix that would make me happy is a command-line configuration
> interface that can comprehensively configure most applications
We have this; check out `kreadconfig5` and kwriteconfig5`.
*** This bug has been marked as a duplicate of bug 397602 ***
--
You are receiving this mail because:
You are watching all bug changes.
