libinput-quirks(1)

📦
version 1.32.0 · 12 versions
, in arch rolling

💅 libinput-quirks(1) — the quirks debug helper, bestie edition

okay so real talk, this page lives in the libinput Manual and it's about the little tool that pokes at libinput's quirks database. yes, quirks. like the weirdo hardware exceptions. it's giving "I know a guy who knows a guy" energy but for device config 🎀

✨ NAME ✨

libinput-quirks — the quirk debug helper for libinput, no cap 🦋

🌸 SYNOPSIS 🌸

libinput quirks list [--data-dir /path/to/dir] [--verbose]
/dev/input/event0

libinput quirks validate [--data-dir /path/to/dir] [--verbose]

libinput quirks --help

🫶 DESCRIPTION 🫶

the libinput quirks tool is literally the one that talks to libinput's quirks database. that's the whole vibe. 🔥

when you run it as libinput quirks list, it lists all the quirks that got applied to the device you handed it. every single one. the way it just reads them out?? iconic. 👑

when you run it as libinput quirks validate, it goes through the quirks files looking for parsing errors, and it fails if it finds one. like a vibe check but for your config files — someone has to be the one to say "girl, this file is broken". 💀

⚠️ as a heads up: this is a debugging tool only. its output and behavior may change at any time. do not rely on the output. fr fr, don't build anything on top of it. 🙈

💜 OPTIONS 💜

  • --data-dir /path/to/dir — use the given directory as the data directory for quirks files. when you leave it out, the default directories are used. easy. ✨
  • --help — print help 🎀
  • --verbose — use verbose output, which is useful for debugging. more words, more clues, iykyk 🕵️‍♀️

🌈 LIBINPUT 🌈

part of the libinput(1) suite, bestie. the whole fam is there. 💖

and that's the whole page, mwah 💋 — this cute lil number ships with libinput 1.32.0, so go forth and debug those quirks, queen 🧚‍♀️⭐

📦 where this page comes from