GSETTINGS-SCHEMA-C(1)

📦 version 3.2.6, in debian bookworm, epel 9, nixos 26.05, ubuntu jammy

💖 GSETTINGS-SCHEMA-C(1) 💖

okay bestie, welcome to the gsettings-schema-convert manual page — it's filed under User Commands and it's literally your little conversion fairy for going from GConf to GSettings. let's get into it 🧚✨

🌸 NAME 🌸

gsettings-schema-convert — GConf to GSettings schema conversion 💅

🎀 SYNOPSIS 🎀

gsettings-schema-convert [option...] {file}

🦋 DESCRIPTION 🦋

so what does this icon actually do?? gsettings-schema-convert converts between GConf and GSettings schema file formats. that's the whole vibe. 🔥

⚠️ real talk though: the conversion is not expected to be fully automated. you are expected to verify and edit the result of the conversion. do not just yolo it and walk away, bestie, that's not the move 😭

also important, no cap: GSettings schemas need to be converted into binary form with glib-compile-schemas before they can be used by applications. so that's a whole extra step you cannot skip. periodt. 👑

✨ Options ✨

  • -h, --help — print help and exit. the classic. 🙈
  • -o OUTPUT, --output=OUTPUT — store the generated output in the file OUTPUT. if no output file is specified, the generated output is written to stdout. 🌈
  • -f, --force — overwrite the output file if it already exists. she's bold, she's decisive, she's not asking permission 💅
  • -g, --gconf — the input file is a GConf schema. telling her what she's working with 🫶
  • -s, --simple — produce a GSettings schema in simple format. the simple format is easier to edit and can be converted into the XML format with gsettings-schema-convert later on. lowkey the cozy option 🍓
  • -x, --xml — produce a GSettings schema in XML format. if the output format is not explicitly specified, this is the default. so if you don't say anything, this is what you get, iykyk ⭐
  • -i ID, --schema-id=ID — use ID as the schema id in the generated GSettings schema. name her, bestie 👑
  • -d DOMAIN, --gettext-domain=DOMAIN — use DOMAIN as the gettext domain in the generated GSettings schema. 🌍
  • -u, --keep-underscores — keep underscores in key names instead of replacing them with dashes. GSettings keys should not contain any underscore. so like... she'll do it, but she's side-eyeing you the whole time 💀

🌈 SEE ALSO 🌈

gsettings-data-convert(1) — a related command to migrate user settings from GConf to GSettings. go read her too, she's part of the lore 💜

and that's the whole page, bestie!! this one's from User Commands, dated 01/21/2013, and it lives under the name GSETTINGS-SCHEMA-C(1) forever and ever 💖✨ mwah, go convert responsibly 🎀

📦 where this page comes from