GTK-QUERY-IMMODULE(1)

💅 GTK-QUERY-IMMODULE(1) — bestie's guide to gtk-query-immodules-2.0 ✨

okay so real quick, this whole page lives inside the GTK-QUERY-IMMODULE(1) manual, and honestly? it's a little niche but it ate.

---

🌸 NAME 🌸

gtk-query-immodules-2.0 — the input method module registration utility 🎀

---

✨ SYNOPSIS ✨

gtk-query-immodules-2.0 [--update-cache] [module...]

---

💖 DESCRIPTION 💖

so gtk-query-immodules-2.0 is out here collecting info about loadable input method modules for GTK+ and then writing all of that into the default cache file location — or just yeeting it to stdout if that's the vibe you want 💫

if you call it with no arguments, it goes looking for modules in the GTK+ input method module path. no cap, it just does its own thing 🔍

if you call it with arguments, it looks for the modules you specified instead. those arguments can be absolute paths or relative paths — either is fine, she's flexible 🦋

normally, the output of gtk-query-immodules-2.0 gets written to libdir/gtk-2.0/2.10.0/immodules.cache, which is exactly where GTK+ looks for it by default. iconic behavior 👑

but listen — if it gets written to some other location, you can set the environment variable GTK_IM_MODULE_FILE to point GTK+ at that file instead. iykyk 🤝

---

💅 OPTIONS 💅

• --update-cache — write the output to the default cache location instead of stdout. literally the "put it in its actual home" flag 🏠

---

🌈 ENVIRONMENT 🌈

• GTK_PATH — you can use this environment variable to prepend directories to the input method module path. front of the line energy ⭐

---

💀 BUGS 💀

None known yet. (yes bestie, that's the entire section. she's flawless so far 🙈✨)

---

🫶 little reminder: keep your paths and your env vars exactly as written — GTK_IM_MODULE_FILE and GTK_PATH are doing very different jobs and you do not want to mix them up, fr fr.

---

this lil page came from [FIXME: source] and it's dated 09/02/2024 — mwah, sending love to whoever wrote it, and to you for reading all the way down here 🧚💜