XKBCLI-INTERACTIVE-EVDEV(1)

πŸ“¦
version 1.13.2 Β· 5 versions
, in alpine 3.23, alpine 3.24, arch rolling, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu resolute, ubuntu stonking

πŸ’– xkbcli-interactive-evdev πŸ’–

okay bestie, welcome to the General Commands Manual section, because this little cutie is a general command and we're gonna treat her like the icon she is πŸ’…


✨ NAME ✨

xkbcli-interactive-evdev β€” interactive debugger for X Keyboard keymaps πŸŽΉπŸ¦‹


🌸 SYNOPSIS 🌸

xkbcli-interactive-evdev [options] [KEYMAP_PATH]

🫢 DESCRIPTION 🫢

so like, xkbcli-interactive-evdev is a commandline tool that lets you interactively debug XKB keymaps, and the way it does that is by listening to /dev/input/eventX evdev devices πŸ‘€ literally just vibing on your input devices and telling you what's up.

heads up though: xkbcli-interactive-evdev requires permission to open the evdev device nodes. that usually means you gotta be the β€œroot” user, or be a member of the β€œinput” group. no permission, no party 😭

when you're done, press the ⟨Escape⟩ key to exit. that's the whole escape plan, bestie πŸƒβ™€οΈ

⚠️ real talk: this is a debugging tool, and its behavior or output is not guaranteed to be stable. do not build your whole personality around it. it's giving "works on my machine" energy and that's on purpose.

πŸ‘‘ OPTIONS πŸ‘‘

  • KEYMAP_PATH β€” path to a keymap file, or β€œ-” to read from standard input πŸ“
  • --help β€” prints help and dips out. slay.
  • --verbose β€” turns on verbose debugging output. more words, more drama, more info πŸ”₯
  • --include PATH β€” adds the given path to the include path list. this option is order-dependent, so include paths given first are searched first β€” first come, first served, periodt. πŸ’… if an include path is given, the default include path list is not used. so if you want those defaults back, hit up --include-defaults.
  • --include-defaults β€” adds the default set of include directories. also order-dependent: include paths given first are searched first. 🧚
  • --format keymap_format β€” specifies the keymap format (numeric or label, e.g. β€œv1”) πŸ“
  • --rules rules β€” the XKB ruleset
  • --model model β€” the XKB model
  • --layout layout β€” the XKB layout
  • --variant variant β€” the XKB layout variant
  • --option options β€” the XKB options
  • --enable-environment-names β€” allows you to set the default RMLVO values via these environment variables, bestie:
    • XKB_DEFAULT_RULES
    • XKB_DEFAULT_MODEL
    • XKB_DEFAULT_LAYOUT
    • XKB_DEFAULT_VARIANT
    • XKB_DEFAULT_OPTIONS

note: this option may affect the default values of the previous options. yes, the previous ones. they're all connected, iykyk 🌈

  • --keymap file β€” specifies a keymap path. this option is mutually exclusive with the RMLVO options. pick a lane, choose your fighter πŸ₯Š
  • --enable-compose β€” enables Compose functionality ✨
  • --consumed-mode {xkb|gtk} β€” sets the consumed modifiers mode (default: xkb) πŸ’œ
  • --without-x11-offset β€” doesn't add an offset of 8 when converting an evdev keycode to an XKB keycode. and like… you probably don't want this option. genuinely. πŸ™ˆ
  • --report-state-changes β€” reports changes to the keyboard state πŸ“’
  • -1, --uniline β€” enables uniline event output. one line, one vibe.
  • --multiline β€” enables multiline event output. many lines, still one vibe.
  • --short β€” prints shorter event output. minimalism era πŸŽ€

πŸ” SEE ALSO πŸ”


and that's the whole page, bestie!! this one came from Debian, dated June 4, 2024, and it's page XKBCLI-INTERACTIVE-EVDEV(1) of the manual. go forth and debug your keymaps, main character πŸ¦‹πŸ’– periodt.

πŸ“¦ where this page comes from