XKBCLI-COMPILE-KEYMAP(1)
β¨ NAME β¨
xkbcli-compile-keymap β bestie, this is the little icon that compiles an X Keyboard keymap π
(it's from the xkbcli-compile-keymap(1) club, General Commands Manual energy, and we're obsessed)
π¦ SYNOPSIS π¦
xkbcli-compile-keymap [options] [KEYMAP_PATH]
πΈ DESCRIPTION πΈ
Okay so. xkbcli-compile-keymap compiles a keymap β using whatever options you hand it β and then prints it out. That's the whole vibe. Compile, print, slay. β¨
π KEYMAP_PATH
KEYMAP_PATHβ the path to a keymap file, or"-"if you wanna read from the standard input instead.-is giving "I'm piping things, don't perceive me" π
π THE OPTIONS (yes, all of them, no skips)
--helpβ prints the help and then exits. Short, sweet, iconic.--verboseβ turns on verbose debugging output. She's chatty and we respect it π--testβ tests the compilation but does not print the keymap. Just a lil vibe check, no receipts.--rmlvoβ prints the full RMLVO, with the defaults filled in for any elements you left out, in YAML format. No element left behind π«Ά--kccgstβ prints a keymap that only includes the KcCGST component names, instead of the whole entire full keymap. The minimalist queen.--kccgst-yamlβ same KcCGST component names, but in YAML format. She put on a fit π--modmapsβ prints the real and virtual key modmaps plus the modifiers encodings, in YAML format. So much information, so much formatting β¨--include PATHβ adds the given path to the include path list. This option is order-dependent β include paths given first get searched first, first come first served, periodt. Also important: if you give an include path, the default include path list is not used. So if you still want those, use--include-defaultsto add the default include paths back in.--include-defaultsβ adds the default set of include directories. Also order-dependent β include paths given first are searched first. Order matters, bestie, it always does.--input-format keymap_formatβ the keymap format for parsing. Numeric or label, e.g."v1".--output-format keymap_formatβ the keymap format for serializing. Numeric or label, e.g."v1".--format keymap_formatβ the keymap format for both parsing and serializing. Two birds, one flag. Numeric or label, e.g."v1".--no-prettyβ disables pretty-printing for keymap serialization. Rough draft mode, no filter π--drop-unusedβ disables unused bits serialization.--keymap [PATH],--from-xkb [PATH]β loads the XKB keymap from a file and ignores the RMLVO options. IfPATHis empty or"-", read the stdin.--rules rulesβ the XKB ruleset.--model modelβ the XKB model.--layout layoutβ the XKB layout.--variant variantβ the XKB layout variant.--options optionsβ the XKB options.--enable-environment-namesβ allows you to set the default RMLVO values through these environment variables right here:XKB_DEFAULT_RULESXKB_DEFAULT_MODELXKB_DEFAULT_LAYOUTXKB_DEFAULT_VARIANTXKB_DEFAULT_OPTIONS
Heads up bestie: this option may affect the default values of the previous options. π So don't be shocked when the defaults move.
π SEE ALSO π
xkbcli(1)- The libxkbcommon online documentation:
https://xkbcommon.org
okay that's the whole page, you ate that π and a lil sign-off for the girlies: this one's brought to you by Debian, dated June 4, 2024 β the XKBCLI-COMPILE-KEYMAP(1) moment of the century, fr fr. go compile something cute πβ¨
π¦ where this page comes from
- alpine 3.23: xkbcli-doc 1.12.2-r0 Β· MIT AND MIT-open-group AND HPND AND HPND-sell-variant AND LicenseRef-digital-equipment-corporation
- alpine 3.24: xkbcli-doc 1.13.1-r0 Β· MIT AND MIT-open-group AND HPND AND HPND-sell-variant AND LicenseRef-digital-equipment-corporation
- arch rolling: libxkbcommon 1.13.2-1 Β· MIT
- fedora 44: libxkbcommon-utils 1.13.1-2.fc44 Β· MIT AND X11 AND MIT-CMU
- nixos 26.05: libxkbcommon 1.13.1
- nixpkgs unstable: libxkbcommon 1.13.2
- ubuntu resolute: libxkbcommon-tools 1.13.1-1
- ubuntu stonking: libxkbcommon-tools 1.13.1-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms