On Tue, 12 Sep 2017 20:39:20 -0400, Adam Tauno Williams wrote: >On Tue, 2017-09-12 at 20:36 -0400, Adam Tauno Williams wrote: >> I can also merrily take my configurations, reliably, from one account >> to another. <https://access.redhat.com/documentation/en-us/red_hat_en >> te >> rprise_linux/7/html/desktop_migration_and_administration_guide/custom >> - >> default-values-system-settings> Which is much better than tar-scp- >> untar+hope-n-pray. > >See "dconf dump {settings-path} > {file}" & "dconf load >{settings-path} {file}".
Actually I was the one who gave the short introduction to dconf usage and I'll repeat myself, dconf is a $HOME in $HOME, but it is not accessible by the tools users of UNIX/POSIX alike systems are used too. To cp, mv or tar individual human readable configurations works completely without issues for apps, if it requires religious rites and hope to do this or Evolution, then the bugs are already in the code of Evolution. Actually an individual human readable config for each app, as well as a binary blob for tons of apps works in the same way option_1=value_x option_2=value_y option_n=value_n Actually $HOME/.config/name_of_the_app directly to human readable files is simpler than a binary blob in $HOME/.config which requires tools to translate it into human readable text and than has to be used /by/a/path/ to the human readable config, too. IOW it's the same as $HOME already provides, with the differences of an additional layer that is good for absolutely nothing, especially since UNIX/POSIX paths do use the "/"-sign and not the "."-sign as required by the gsettings command. dconf gains absolutely nothing, it just adds a completely useless, annoying layer. _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
