3 ms·
gsetttings list-recursively > gsettings-all.txt The reverse action is left as an exercise to the reader. Or wait.. for line in $(cat gsettings-all.txt); do
by vrotaru 15y ago
gsetttings list-recursively > gsettings-all.txt
The reverse action is left as an exercise to the reader. Or wait..
for line in $(cat gsettings-all.txt); do gsettings set $line; done
PS. Ubuntu can be blamed for Unity, which is just another shell (maybe not the last) but that settings stuff is way beyond their influence.
- kragen 15y agoHey, I'm still using an old version of GNOME; would you be willing to post the output of gsettings list-recursively | wc gsettings list-recursively | gzip -9c | wc -c to help us understand the issues?
- vrotaru 15y ago$ gsettings list-recursively | wc 1037 3367 56466 $ gsettings list-recursively | gzip -9c | wc -c 11700 Here. What is the issue you are trying to understand? $ gsettings list-schemas | wc -l 211 I guess we can assume a schema == a config file
- kragen 15y agoThank you very much. The issue I'm trying to understand is exactly how the fuck it is so fucking slow to parse 56 fucking kilobytes of text at session login time that it justifies encrypting my fucking desktop settings in a fucking binary configuration file. I thought maybe the default configuration had ten megabytes of shit in it or something, which could conceivably sort of explain it, although then that would be another fucking stupid decision that would require explanation. But 56 fucking kilobytes? Which gzip suggests would be 35 kilobytes with a human-oriented syntax? Give me a fucking break.
- vrotaru 15y agoThe issue is not as much parsing as reading from a lot of different files. As someone else has put it in other thread sequential reading is fast. Random reading from 50+ files which involves seeking the disk is not. Of course the gconf configuration may have had other alternatively smart ways of doing things and gsettings authors are just optimizing where it is easy to do. And by the way the gconf stuff is still necessary sudo apt-get remove gconf2 shows the a whole lot of packages which still depend on it, so when the transition will be complete there will be more than "56 fucking kilobytes of text"
- kragen 15y agoSticking all the stuff you need to read at login time into one file is at least plausibly reasonable (although! ldd /usr/bin/gnome-terminal | wc alone still gives me 52 libraries, so config files are not close to the only problem here!) but turning that one file into an opaque binary file is not.