So the first thing I would try is simply to choose a new random UUID and start setting the profile parameters at that UUID using gsettings set. If you launch dconf-editor and browse the settings, you will see this hierarchy: org
I am not sure where the weird path syntax is described (if anywhere at all), but it very much seems that everything after the first colon is just a single long dconf path – there doesn't seem to be any meaning to the :/:foo and those colons just become part of the "folder" name. (This is somewhat of an ugly way to implement it, but that's how it is.) Terminal.) dconf dump /org/gnomeīut GNOME Terminal needs multiple instances, so it uses a feature called "relocatable schemas" where the dconf storage path is specified explicitly instead of being automatically determined from the schema XML description. (Though the schema can override this, hence the mismatch between /terminal and. Usually, each GSettings schema has only one instance and the schema name directly maps to a single dconf location – is stored as a folder /org/gnome/Foo in dconf.
GSettings enforces strong typing and schema compliance while the underlying dconf only stores keys/values without any checking. GSettings is an abstract interface over some platform-specific settings storage API, for example, Registry on Windows or dconf on Linux.
0 kommentar(er)
