libinput-m...d-pressure(1)

πŸ“¦
version 1.32.0 Β· 2 versions
, in alpine 3.24, arch rolling, centos-stream 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu resolute, ubuntu stonking

πŸ’– libinput-m...d-pressure(1) πŸ’–

okay so bestie, welcome to the General Commands Manual page for libinput-measure-touchpad-pressure, which is genuinely one of the cutest little debugging tools in the whole libinput family. grab a snack, we're measuring vibes. πŸŽ€


✨ NAME ✨

libinput-measure-touchpad-pressure β€” measure pressure properties of devices


🌸 SYNOPSIS 🌸

libinput measure touchpad-pressure [--help] [options] [/dev/input/event0]

πŸ¦‹ DESCRIPTION πŸ¦‹

So the libinput measure touchpad-pressure tool measures the pressure of touches on a touchpad. it's an interactive tool, okay? like, not a "run it and walk away" situation. when you execute it, it will prompt you to interact with your touchpad β€” yes, that means you, bestie, touching the touchpad with your actual fingers. πŸ’…

when it terminates, the tool prints a summary of the pressure values it saw. and like… this data? it should be attached to any pressure-related bug report. fr fr, do not skip this step, the maintainers need the receipts. πŸ“‹βœ¨

if you want the full description of how libinput's pressure-to-click behavior works, go read the online documentation here:

⚠️ not me having to say this but: this is a debugging tool only. its output may change at any time. do not rely on the output. it's giving chaotic on purpose, periodt. πŸ’€

also β€” this tool usually needs to be run as root so it can actually access the /dev/input/eventX nodes. no root, no touchy. πŸ™ˆ


πŸ’… OPTIONS πŸ’…

okay so first thing, the device node situation:

  • if a device node is given, this tool opens that device node. straightforward, iconic.
  • otherwise, this tool searches for the first node that looks like a touchpad and uses that one. it just picks one, no cap. πŸ“

here are your actual options:

  • --help β€” print help. the classic. your bestie in every situation. 🫢
  • --touch-thresholds="down:up" β€” set the logical touch pressure thresholds to down and up, respectively. so here's the tea: when a touch exceeds the pressure in down, it's considered logically down. and if a touch is logically down and then goes below the pressure in up, it's considered logically up. these thresholds have to be in device-specific pressure values, and it is required that down >= up. like, that's not optional, that's the rule. ⭐
  • --palm-threshold=N β€” assume a palm threshold of N. the threshold has to be in device-specific pressure values. 🌸
  • --thumb-threshold=N β€” assume a thumb threshold of N. the threshold has to be in device-specific pressure values. 🌈

and here's the little plot twist: if the touch-thresholds or the palm-threshold are not provided, this tool uses the thresholds provided by the device quirks (if any) or the built-in defaults. so like, it's got your back either way, bestie. 🧚


πŸ‘‘ LIBINPUT πŸ‘‘

Part of the libinput(1) suite. iykyk. πŸ’œ


and that's the whole page!! mwah πŸ’‹ this one lives in the General Commands Manual, and the footer on the original was literally just libinput-m...d-pressure(1) all over again β€” so hey, consider yourself signed off, you absolute icon. go forth and measure those pressure values, main character. slay ✨