keyfuzz(8)

🎀 KEYFUZZ(8) 🎀

ok so bestie, welcome to keyfuzz — the System Manager's Manual page you didn't know you needed, but lowkey do.

---

✨ NAME ✨

keyfuzz — Modify keyboard scancode tables of the Linux input layer 💅

🦋 SYNOPSIS 🦋

keyfuzz [options]

that's it. that's the whole invocation. no positional args, no drama. periodt.

🌸 DESCRIPTION 🌸

okay so here's the tea: you use keyfuzz to manipulate the scancode/keycode translation tables of keyboard drivers that support the Linux input layer API — aka the "evdev API", iykyk. literally its whole personality is remapping your keyboard's brain. no cap. 🧠✨

💖 OPTIONS 💖

• -g, --get — dump the current scancode translation table of the device to STDOUT. it's giving "screenshot but for your keymap" 📸
• -s, --set — merge the translation table you pass through STDIN into the current translation table of the device. feeding it keys so it can feed you keys, iconic 🔥
• -i, --info — show some information about the specified device. just a lil vibe check 👑
• *-d, --device=DEVICE* — use the specified event device. the virtual file /proc/bus/input/devices lists all input devices available on the local system. (Default: /dev/input/event0) 🎀
• -v, --vebose — enable verbose mode. if used together with --set, all translation tables changes are printed to STDERR. yes bestie, the flag is spelled --vebose in the man page and we are respecting it fr fr, no correcting, we don't do that here 💀🫶
• -h, --help — show help. our fave low-stakes option 🌈
• -v, --version — show version. and yes, -v is listed twice on this page — once for --vebose and once for --version — and honestly? not me noticing that. very main character energy of the original author. keeping it exactly as written, amen 🙈

ngl, that double -v is a whole situation. we are simply reporting it, not fixing it. no inventing, no merging, no "helpful" edits. 💅

⭐ TRANSLATION TABLES ⭐

okay this is the part where you actually learn the format, so listen up bestie:

the scancode/keycode translation tables — as read from STDIN or written to STDOUT — are formatted like this:

• lines beginning with a hashmark and empty lines are ignored
• all other lines have to contain a scancode and a keycode number separated by white space
• the numbers may be specified either in decimal or in hexadecimal notation
• in the latter case, a 0x has to be prepended

so a line is basically <scancode> <keycode> and the parser is chill about hex as long as you bring the 0x. 🍓

and here's the workflow, chef's kiss:

1. save the current table by passing --get to keyfuzz and storing its output in a file
2. restore the table by passing the contents of that file back to keyfuzz with --set

backup and restore, but make it keyboard. obsessed. 🧚✨

👑 AUTHOR 👑

keyfuzz was written by Lennart Poettering <mzxrlshmm (at) 0pointer (dot) de>.

keyfuzz is available at http://0pointer.de/lennart/projects/keyfuzz/ — go show some love, the link is literally right there 🫶

💜 COMMENTS 💜

This man page was written using xmltoman(1) by Oliver Kurth. respect the craft, fr fr. 🎀

---

and that's the whole page, bestie! this one came from the Manuals collection, User manual section, and it's keyfuzz(8) — so if you ever need to find it again, that's your receipt. slay, go remap something, and remember: back up your table first 😭💖