diff --git a/content/fixing-bad-trackpoints.md b/content/fixing-bad-trackpoints.md index 80e53bd..287920e 100644 --- a/content/fixing-bad-trackpoints.md +++ b/content/fixing-bad-trackpoints.md @@ -26,7 +26,7 @@ Luckily though I was able to stumble upon [a random Arch Linux forums thread](ht ``` sudo evtest --grab /dev/input/event21 | perl -ne 'system("xdotool mouse".($2?"down ":"up ").($1-271)) if /Event:.*code (.*) \(BTN.* value (.)/' ``` -*"k395"'s oneliner solution* +*"k395"'s one-liner solution* I had to do a bit of modification here though. First of all, I needed to determine exactly what `/dev/input/event` node was the one for my trackpoint. Luckily, running `evtest` with no arguments enters an interactive mode that lets you see what each event node maps to. Unfortunately I haven't found a way to get this programatically, but these seem to be stable across reboots so simply grabbing the correct value is sufficient for me. In my case, the node is `/dev/input/event6` for the `Elantech TrackPoint`. @@ -58,7 +58,7 @@ Select the device event number [0-17]: ^C But that wasn't the only issue. Unfortunately this basic implementation lacks support for the *middle* mouse button, and given that I use it quite extensively (for Linux middle-button quickpaste, closing tabs in Firefox, etc.), I needed that functionality. -This prompted me to rewrite the Perl-based oneliner into a slightly easier to read Python version, and implemented middle button support as well. I also added a bit of debouncing to avoid very rapid presses resulting in 2 `xdotool` events in very rapid succession. I then put everything together into a script which I called `disable-trackpoint`. +This prompted me to rewrite the Perl-based one-liner into a slightly easier to read Python version, and implemented middle button support as well. I also added a bit of debouncing to avoid very rapid presses resulting in 2 `xdotool` events in very rapid succession. I then put everything together into a script which I called `disable-trackpoint`. ``` #!/bin/bash