EVEMU-DEVICE(1)

πŸ’– EVEMU-DEVICE πŸ’–

okay bestie, sit DOWN, because we're talking about evemu-device(1) β€” and also evemu-play and evemu-event, they're all in here, it's a whole trio, it's giving girl group πŸ’…βœ¨


🌸 NAME 🌸

evemu-device, evemu-play, evemu-event β€” make a virtual input device and replay an event sequence πŸŽ€ no cap, that's literally the whole job.


✨ SYNOPSIS ✨

evemu-device [description-file]

evemu-play /dev/input/eventX < event-sequence
evemu-play event-sequence.txt

evemu-event /dev/input/eventX [--sync] --type <type> --code <code> --value <value>

look at those three little lines just vibing πŸ¦‹ each one is a different sister, and they all ate.


πŸ’œ DESCRIPTION πŸ’œ

okay so first up, evemu-device β€” she creates a virtual input device based on the description-file. and where does that description come from? usually from evemu-describe(1), she's the one who wrote it πŸ’–. then evemu-device goes and creates a new input device with uinput, and prints the name and the device file to stdout. iconic behaviour, honestly.

then we have evemu-play β€” she replays the event sequence that you hand her on stdin, and she pushes it through the input device. the event sequence must be in the form created by evemu-record(1), that's non-negotiable bestie, she has standards βœ‹. and here's the cute part: if the argument is a file containing a recording, evemu-play creates the device and prompts the user for an interactive replay of the events. interactive!! main character energy fr fr πŸ‘‘

and last but not least, evemu-event β€” she plays exactly one event, with the current time. just one. a single little event, one and done πŸ“. and if you pass --sync, then evemu-event generates an EV_SYN event after the event. the event type and code may be specified as the numerical value or the symbolic name from linux/input.h β€” so you can be a numbers girlie or a names girlie, both are valid πŸ’….

🚨 okay important bit, don't scroll past this: evemu-device must be able to write to the uinput device node, and evemu-play must be able to write to the device node specified. in most cases this means it must be run as root. yes, root. I know. but that's the vibe check and she passed it, so. 😭

🌈 SEE ALSO 🌈

the whole friend group, go say hi 🫢


πŸ‘‘ AUTHOR πŸ‘‘

evemu was written by Henrik Rydberg <rydberg@euromail.se> β€” thank you king, we appreciate you πŸ’–βœ¨


πŸ“ NOTES πŸ“

  1. rydberg@euromail.se mailto:rydberg@euromail.se

and that's the whole page bestie, you understood it, you devoured it, slay πŸ’…πŸ¦‹πŸŒΈ

signing off from 12/14/2016, this was EVEMU-DEVICE(1) β€” go create a virtual input device, ily, bye πŸ’œ

πŸ“¦ where this page comes from