INPUTPLUG(1)
π INPUTPLUG(1) π
okay bestie, sit down, hydrate, because i'm about to tell you about inputplug β it's an XInput event monitor and honestly? it's giving main character energy for your X server. β¨
πΈ SYNOPSIS πΈ
inputplug [-v] [-n] [-d] [-0] -c command-prefix
inputplug [-h|--help]
like, that's the whole vibe. no cap. π«Ά
β¨ DESCRIPTION β¨
so inputplug is a daemon. she connects to a running X server and justβ¦ watches. π specifically she monitors the XInput hierarchy change events, and those little cuties show up whenever a device gets attached or removed, enabled or disabled, etc. literally every time the device tree does a lil dance, she knows. π
when a hierarchy change happens, inputplug parses the event notification structure and calls the command you specified with command-prefix. and the command gets four arguments, in this exact order:
command-prefix event-type device-id device-type device-name
so the event type? it may be one of these icons: π
XIMasterAddedXIMasterRemovedXISlaveAddedXISlaveRemovedXISlaveAttachedXISlaveDetachedXIDeviceEnabledXIDeviceDisabled
and the device type? may be any of these queens: π
XIMasterPointerXIMasterKeyboardXISlavePointerXISlaveKeyboardXIFloatingSlave
the device identifier is an integer (just a number, bestie, nothing fancy). and the device name may have embedded spaces β so watch out for that when you're handling it. π
π OPTIONS π
here's a lil summary of the options, bestie, because you deserve to know:
-h,--helpβ show help. and--helpshows more details (she's an overachiever, we love her for it). π-vβ be a bit more verbose. just a bit. a sprinkle of extra talking. β¨-nβ start up, monitor events, but don't actually run anything. and if you've got verbose mode on, she'd print the actual command she would have run. also this one implies-d, sneaky little thing. π-dβ don't daemonise. run in the foreground. stay with me, i'm right here. π₯Ί-0β on start, trigger added and enabled events for each plugged device. a master device will trigger the"added"event, while a slave device will trigger both the"added"and the"enabled"event. double the events, double the fun. π-c command-prefixβ the command prefix to run. unfortunately, currently this is passed toexecvp(3)directly, so spaces aren't allowed. yeah, i know, it's a whole thing. this is subject to change in future, so keep an eye out. π-p pidfileβ write the process ID of the running daemon to the filepidfile. cute lil paper trail. π
π¦ ENVIRONMENT π¦
DISPLAYβ the X11 display to connect to. that's it, that's the one. π
π SEE ALSO π
π COPYRIGHT π
Copyright (C) 2013, 2014, 2018, 2020, 2021 Andrej Shadura.
Copyright (C) 2014, 2020 Vincent Bernat.
Licensed as MIT/X11.
π AUTHOR π
Andrej Shadura <andrewsh@debian.org>
okay that's the whole page bestie, you ate that, fr fr. π β¨
and just so you have the receipts β this lil masterpiece is dated 2020-11-01 and it lives under the manual name INPUTPLUG(1) in the INPUTPLUG(1) section. slay, go plug in a device and watch the magic happen. ππ«Ά
π¦ where this page comes from
- debian bookworm: inputplug 0.4.0-2 Β· MIT
- debian trixie: inputplug 0.4.0-4 Β· MIT
- nixos 26.05: inputplug 0.4.0
- nixpkgs unstable: inputplug 0.4.0
- ubuntu jammy: inputplug 0.4.0-2 Β· MIT
- ubuntu noble: inputplug 0.4.0-4build1 Β· MIT
- ubuntu questing: inputplug 0.4.0-4build1
- ubuntu resolute: inputplug 0.4.0-4build2 Β· MIT
- ubuntu stonking: inputplug 0.4.0-5 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms