geistest(1)

💖 geistest — ok bestie, let's talk GEIS 💖

so like, this is the manual for geistest, which is the test operation of the GEIS API. yes it's geistest(1), section 1, we stay in our lane. 🎀

✨ SYNOPSIS ✨

geistest [ -w windowid ] [ -d deviceid ]

that's it. that's the whole vibe. two optional flags, zero drama. 🦋

🌸 DESCRIPTION 🌸

okay so picture this: geistest is a test driver. its whole job is verifying that gestures get recognized and propagated correctly through the GEIS API. like, is the gesture happening? does it travel where it's supposed to? bestie we are checking. 👑

and the exit?? hitting any key on the keyboard will exit the program gracefully. literally any key. no Ctrl+C chaos required, no kill -9 disrespect. just tap something and she leaves politely. periodt. 💅

⭐ OPTIONS ⭐

• -w — gives you the windowId of one specific window to associate with gestures. super duper useful with touchscreens, like genuinely. if you don't set this argument, the default action is to read gestures on all windows. all of them. the whole building.

you can figure out the windowId using the program xwininfo. go get it bestie. 🔍

• -d — gives you the deviceId of one specific input device to be tested for multi-touch gestural input. if you don't set this argument, the default action is to listen to multi-touch input on all devices.

and this one can be used more than once to specify multiple input devices!! stack those -ds, we love a repeatable flag. 🫶

you can figure out the deviceId using the program xinput.

🌈 ENVIRONMENT 🌈

• GEIS_DEBUG — turns on GEIS library diagnostic messages on stderr. it's giving "tell me everything that's happening" energy. 🐛

👑 SEE ALSO 👑

• gesturetest(1)

💀 reminder bestie: no -w means all windows, no -d means all devices. the defaults are loud. know that before you go tapping things. ✨

and that's the whole page!! this lil gem is from August 16, 2010, it lives in the geistest(1) manual section, and yes she's an icon, she's a legend, and she is the moment. mwah 💖🎀🦋