GNOME Bugzilla – Bug 795179
gsettings list-recursively does not output paths while schema/key/value are path-dependent
Last modified: 2018-05-24 20:24:52 UTC
"gsettings list-recursively" just outputs schema/key/value lines, without the corresponding path. The problem is that such lines are path-dependent. For instance, the "gsettings list-recursively" output concerning org.gnome.evolution.window on one of my machines is: org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 org.gnome.evolution.window width 0 org.gnome.evolution.window maximized false org.gnome.evolution.window height 0 org.gnome.evolution.window x 0 org.gnome.evolution.window y 0 Here, for each given key, the value is the same. But the value may depend on the path. Without the path, such output does not makes much sense, and there is even a loss of information (the goal is to keep some form of human-readable backup of my current config). Bug reported as a followup of: https://bugzilla.gnome.org/show_bug.cgi?id=723003#c12
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1365.