Another irritation with Gnome's gconf settings systemAs if the first irritation wasn't enough, there's another problem with the Gnome settings stuff. It is this: modern Gnome applications keep all of their settings locked up inside gconf, even things that you enter and that in another, simpler era would have been stuck in dotfiles somewhere. This has a practical issue that I have been running into after learning about convenient ssh in Gnome; it's hard to move settings for something from machine to machine. Consider the mini-commander applet macros, which are stored as gconf settings. I'd like to be able to just copy improvements I make from system to system (instead of having to re-enter them), and to easily install the setup on new machines. With dotfiles, this would be obvious; with gconf, what I have is in practice an opaque blob. (To its credit, sshmenu does have an actual dotfile for its host information that I can just copy around.) In theory, one can use tools like Part of the problem is that, of course, applications are not organizing
their keys for your convenience; in this sort of case, they're using
gconf as a datastore. The mini-commander applet makes a good example;
as far as I can tell, it stores its macros in two keys (both in
(Disclaimer: it's possible that the mini-commander applet is a bad example and that good Gnome programs don't act this way. I'm not really optimistic, though.) (One comment.)
|
These are my WanderingThoughts GettingAround This is part of CSpace, and is written by ChrisSiebenmann. * * * Atom feeds are available; see the bottom of most pages. Categories: links, linux, programming, python, snark, solaris, spam, sysadmin, tech, unix, web |