gnome-extensions enable UUID
gnome-extensions disable UUID
gnome-extensions reset UUID
gnome-extensions info UUID
gnome-extensions show UUID
gnome-extensions list [OPTION...]
gnome-extensions prefs UUID
gnome-extensions create [OPTION...]
gnome-extensions pack [OPTION...]
gnome-extensions install [OPTION...] PACK
gnome-extensions uninstall UUID
The command will not detect any errors from the extension itself, use the info command to confirm that the extension state is ENABLED.
If the extension is already enabled, the command will do nothing.
If the extension is not enabled, the command will do nothing.
The extension will be disabled in GNOME, but may be enabled by other sessions like GNOME Classic.
pack [OPTION...] [SOURCE-DIRECTORY]
The bundle will always include the required files extension.js and metadata.json, as well as the optional stylesheet.css and prefs.js if found. Each additional source that should be included must be specified with --extra-source.
If the extension includes one or more GSettings schemas, they can either be placed in a schemas/ folder to be picked up automatically, or be specified with --schema.
Similarily, translations are included automatically when they are located in a po/ folder, otherwise the --podir option can be used to point to the correct directory. If no gettext domain is provided on the command line, the value of the gettext-domain metadata field is used if it exists, and the extension UUID if not.
All files are searched in SOURCE-DIRECTORY if specified, or the current directory otherwise.
install [OPTION...] PACK
The command unpacks the extension files and moves them to the expected location in the user’s $HOME, so that it will be loaded in the next session.
It is mainly intended for testing, not as a replacement for GNOME Software or the extension website. As extensions have privileged access to the user’s session, it is advised to never load extensions from untrusted sources without carefully reviewing their content.