It is not possible to do this with
gsettings, as the option simply does not exist. There is extensive documentation on
gsettings and the internals of the program at the official Gnome site.
However, there is an interesting project at github called
gsettings-info that does exactly what you ask. It is a script that queries information about either schemas and/or keys from the gschema information and returns the same data about them that is displayed when you use
You'll requiere Git and git xsltproc (library that it uses to read the gschema information)
sudo apt install git xsltproc
Obtain the program with:
git clone git://github.com/jmatsuzawa/gsettings-info.git
Now you can run the script
You can either run it from the home folder (and occasionally update it by going to the folder and using
git pull), or install to the system or place it in your
~/bin folder so it is available by just entering
If you are running it from the downloaded folder, entering
./gsettings-info help will give all the options, as does the README and the information at the Github page.
You can find much information on both the schemas and keys. Here is an example of how to find data about certain keys. This assumes it is run from the downloaded folder, and so
./ is needed to run the script.
To find out details about the particular keys of the chosen schema, enter:
./gsettings-info desc org.gnome.gnumeric.autocorrect
init-caps: Autocorrect initial caps
init-caps-list: Autocorrect initial caps
first-letter: The autocorrect engine does not correct the initial caps for words in this list.
first-letter-list: The autocorrect engine does not correct the first letter for words in this list.
names-of-days: Autocorrect names of days
replace: Autocorrect replace
To show defaults and information for a particular key, use:
./gsettings-info show org.gnome.gnumeric.autocorrect init-caps
SUMMARY: Autocorrect initial caps
DESCRIPTION: Autocorrect initial caps
This seems to be exactly what your are looking for, and is about the only way to show this information on the command-line instead of in