One other feature

Posted Jan 8, 2009 22:54 UTC (Thu) by job (guest, #670)
In reply to: One other feature by smitty_one_each
Parent article: BleachBit: Does GNU/Linux need the equivalent of a Windows registry cleaner?

I disagree. That would add complexity and make it harder to use. A single _place_ however is a good idea, and that place is $HOME.

One other feature

Posted Jan 9, 2009 4:32 UTC (Fri) by k8to (guest, #15413) [Link] (3 responses)

No I agree with the grandparent.

We should have a single interface for accessing configuration data, and a single set of code for managing it. Fortunately this is already written, and it is called the filesystem.

One other feature

Posted Jan 10, 2009 12:03 UTC (Sat) by mlankhorst (subscriber, #52260) [Link] (2 responses)

It exists... gnome uses gconf, kde uses .kde/share/apps/appname ;)

One other feature

Posted Jan 24, 2009 22:53 UTC (Sat) by muwlgr (guest, #35359) [Link] (1 responses)

What is really needed, is probably sometihing like "KDE config keeper/explorer/reverter". To keep your configs in .git on each KDE startup. And let you see what so smart had KDE done with each config at what time. And of course return that into some previous state when everything looked and worked well. As KDE and its apps are prone to do some voluntary and overly-intellectual reconfigurations and fallbacks which the user only has to guess about how to revert or "fallforward".

One other feature

Posted Jan 25, 2009 23:59 UTC (Sun) by dlang (guest, #313) [Link]

this sort of thing is very useful for many different programs nowdays. I ended up setting up a cron job to do a commit of 'interesting' files every min. it has saved me a few times when applications go haywaire (most commonly with firefox)

David Lang