KDE

5253 readers

77 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

[email protected]

Proposal for cleaner ~/.config directory (rabbitictranslator.com)

submitted 1 year ago by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

There's a proposal at the linked blog post for how to clean up the config directory.

The post goes into detail which changes would be required in KDE software using Qt.

After reading, I just have one question (the blog does not seem to have a comment section): how does this handle transitioning from the old location to the new location? Imagine having a katerc config file under ~/.config and one under ~/.config/kate (which is the suggestion from the post) - should those be merged once and then the old one gets deleted?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 1 year ago (3 children)

@MartinR the Maven convention for packaging is a group identifer/package is the inverse domain order.

Taking plasma-org.kde.desktop-appletsrc you would create a group identifer of: org.plasma.kde.desktop With the artefact identifier being: appletsrc.

The folder structure would then look like:

.config  
\-\>org  
\-\>-\>plasma  
\-\>-\>-\>kde  
\-\>-\>-\>-\>desktop  
\-\>-\>-\>-\>-\>appletsrc

Its simple

[–] [email protected] 1 points 1 year ago

The proposal isn't mine, I just read and shared it :-) The blog post has a paragraph or two about multpile subfolders, as I read it, the specification is not clear on whether thats supported? But actually: at first glance I think this would be better to have, because it would possibly make synchronizing to a new PC/Laptop even easier. However, this only works if any machine-specific settings (e.g. "offset /size of window") are not stored in config, as that might break if you sync config between a multi-monitor setup and a single-monitor setup. This requires a lot of thought...

[–] Molecular0079 1 points 1 year ago (1 children)

That feels way too nested to be useful IMHO. It's great for packaging dev tools, but not really for handling config directories for user space apps. I just want ~/.config/KDE/<app>

[–] [email protected] 1 points 1 year ago

@Molecular0079 that is a starting point.

Once you start laying out directories, I suspect you will find a root level everything lives in. You flatten the hierarchy so you have one folder jumping to that level.

[–] [email protected] 1 points 1 year ago

I always considered plasma to be a part/sub project of kde, therefore org.kde.plasma would seem correct-er.