Timeline for Running a script based on raw events from a specific HID?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10 at 6:35 | comment | added | nbanba | Ok very fast on my laptop... that should be due to the buffer. You can try to replace -oL -eL by -o0 -e0 or to remove stdbuf command: exec {fd0}< <(sudo libinput debug-events --device /dev/input/event6 | grep POINTER_MOTION); $ while read -u ${fd0}; do echo $(date '+%s.%N'); done which result on my laptop when touching the touchpad in: 1744266769.882982496 1744266769.884502495 1744266769.885960178 1744266769.887497719 1744266769.889060294 1744266769.890775222 1744266769.892475762 1744266769.894335805 1744266769.896346523 ... | |
| Apr 10 at 1:48 | comment | added | Gridzbi Spudvetch | Ok, I'm not sure what's causing this but this script (once I got it working) runs incredibly slowly. I swapped out the event number and relevant action, and replaced echo pointer move with date, and it's clear that it's not running properly. I can spam the hell out of the volume buttons for >10 seconds and it shows nothing, then I get a whole slew of date outputs all from the same second. Really weird. | |
| Apr 9 at 7:26 | comment | added | nbanba | example: exec {fd0}< <(sudo stdbuf -oL -eL libinput debug-events --device /dev/input/event6 | grep POINTER_MOTION) ; while read -u ${fd0}; do echo pointer move; done ; pointer move pointer move pointer move ... CTRL+C | |
| Apr 9 at 7:20 | comment | added | nbanba | This script is working fine on my debian12 laptop. You should add sudo to stdbuf command if you encountered the error: ` Failed to open /dev/input/eventX` | |
| Apr 8 at 23:29 | comment | added | Gridzbi Spudvetch | This script seems to end/crash immediately upon running, without waiting for any key input. (I've made sure to run it as root.) | |
| Apr 7 at 7:38 | history | answered | nbanba | CC BY-SA 4.0 |