geisview(1)

💖 geisview — the manual page, but make it cute 💖

okay bestie, so this is geisview from section 1 of the manual, and honestly? she's a little legend. let's get into it. ✨

🌸 NAME 🌸

geisview — view operation of the GEIS API

🎀 SYNOPSIS 🎀

geisview [ -V ] [ -w windowid ] [ -b backend ]

🦋 DESCRIPTION 🦋

So like, this manual page is here to explain the geisview program to you, bestie. And what is geisview, you ask? It's a test driver — like, its whole job is verifying the recognition and propagation of gestures through the GEIS API. that's it, that's the gig. it shows you the operation of the GEIS API and it does it with main character energy. periodt. 💅

✨ OPTIONS ✨

• -V — prints the version number of the program and then dips. exits immediately. bye! 👋
• -w — specifies the windowId of a specific window to associate with gestures. highkey useful with touchscreens, ngl. If you don't set this argument, the default action is to read gestures on the root window. so like, no windowid? root window. that's the vibe.

You can figure out the windowId using the program xwininfo. (she's the plug for that. 🫶)

• -b — specifies the recognizer back end to use.

These are the valid back end selections, no cap:

• dbus — uses the DBus back end to connect to a running GEIS server (default).
• grail — uses the dynamically loaded grail back end (default fallback).
• mock — uses a mock back end for testing.
• xcb — uses the pre-XI2 back end (may not be available 👀).

🌈 ENVIRONMENT 🌈

• GEIS_DEBUG — enables GEIS library diagnostic messages on stderr. so if you're like "why is this happening", she'll tell you. on stderr. loudly. 💀

👑 SEE ALSO 👑

• geistest(1)

okay that's the whole page, bestie, you ate that 🍓💜

this was geisview(1) from the geisview manual, and the source is dated February 12, 2013 — yeah, she's an elder icon but she still slays. mwah. 🎀✨🦋