KDE / Plasma configuration

[tobiasBora]

Hello,

First, thanks a lot for this great project. I'd like to use it to configure my KDE/plasma, for example to keep track of the theme, but I was not able to find in the manual any reference to it. Is it because KDE is not configurable by this project, or is it because I missed something?
Thanks!

[uvNikita]

Hi!

You can see the supported options in this online manual: https://rycee.gitlab.io/home-manager/options.html. As far as I know, KDE configuration is not supported at the moment and, unfortunately, I'm not sure how much work it would take to implement it.

That said, if KDE configuration is stored as text files, it should be relatively simple. You can check other modules to get an idea of how to implement it.

[mestaritonttu]

See also #607

[stale]

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[AleXoundOS]

The principle point here I think is coexistence of KDE "System Settings" application with declarative home-manager configuration. So the workflow is not clear. KDE settings application may replace symbolic links with new files or refuse to do it confusing the settings application. Both situations may produce unexpected results for the end user.
But overall, I think making KDE settings configurable declaratively would be a huge breakthrough for both KDE and home-manager.

[tobiasBora]

True. But we can imagine something in between : KDE seems to ask to users to use a command line utility to modify the settings instead of modifying some files : maybe we could create "declaratively" a script that runs the appropriate commands, and let the users run this script when they want to change KDE's configuration via home manager and/or periodically. It's not truly declarative (except maybe if we cover all configurations and if we put in read-only mode all files, which may not be desirable) but that way a user could both configure KDE declaratively and via the graphical tools.

[AleXoundOS]

KDE seems to ask to users to use a command line utility to modify the settings instead of modifying some files

It seems kwriteconfig is this command line utility.
Though, nix won't know if a user has changed settings via "System Settings", so changes won't be permanent. But it's another story.

[tobiasBora]

Yes exactly thanks. Well changes via "System Settings" will be permanent if they are not overwritten by nixos' script I guess.

[AleXoundOS]

Nice hypothesis.

[kennyballou]

There seems to be clear overlap between this issue and #607. Can we close this in favor of #607 since most of the context and items discussed here are already covered?

[berbiche]

Closing this in favor of #607.
Please move the discussion over to #607. 😃