VOID(4)

📦 version 1.4.2, in arch rolling, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

💜 VOID(4) 💜

ok so this is the void page from the Kernel Interfaces Manual, bestie. yes that VOID(4) — the null input driver. buckle up, it's a whole vibe.

✨ NAME ✨

void — the null input driver, aka the driver that literally does nothing and is iconic for it 💅

🎀 SYNOPSIS 🎀

drop this into your config and you're done:

Section "InputDevice"
  Identifier "idevname"
  Driver "void"
  ...
EndSection

🌸 DESCRIPTION 🌸

okay so void is a dummy/null Xorg input driver. like, a placeholder. a ghost 👻

it does not connect to any physical device — nope, none, zero — and it never delivers any events. not one. it's giving silent treatment, and honestly? that's the whole point.

the way it works: it functions as both a pointer device and a keyboard device, and it can be used as the X server's core pointer and/or core keyboard. yes bestie, dual threat energy 🫶

its purpose (and this is the main character detail) is to let X servers pre version 1.4 operate without a core pointer and/or core keyboard. that's it. that's the job. slay.

⭐ CONFIGURATION DETAILS ⭐

for the general config tea, go read xorg.conf(5) — it's got all the deets plus the options that work with all input drivers 💖

but this driver? this one? it doesn't have any configuration options in addition to those. none. nada. it's minimalism, it's a clean aesthetic, it's lowkey perfect 🌈

🦋 SEE ALSO 🦋

ngl if you came here looking for options to tweak, there are none — this driver's whole personality is doing nothing, and it ate 💀

kiss kiss, this page was brought to you by X Version 11 and xf86-input-void 1.4.2 — mwah, go touch some grass (not a physical device tho, this driver won't connect to it) 🍓🧚💜

📦 where this page comes from