xlibinput_calibrator(8)
π NAME π
okay so bestie, welcome to xlibinput_calibrator(8) β from the General Commands Manual β the main character whose whole job is to calibrate a X11 touch screen device. that's the assignment, and she ate π
β¨
π SYNOPSIS π
xlibinput_calibrator [--output-file-x11-config=<filename>] [--dont-save]
[--output-file-xinput-cmd=<filename>] [--verbose]
[--threshold-misclick=<nn>] [--matrix=_x1,x2..x9_]
[--threshold-doubleclick=<nn>] [--show-matrix]
[--device-name=<devname>|-device-id=<device-id>]
[--show-x11-config] [--show-xinput-cmd]
[--monitor-number=<nr>] [-display=<display>]
xlibinput_calibrator --list-devices
π¦ DESCRIPTION π¦
xlibinout_calibrator(8) calibrates a touch screen by setting the so-called libinput matrix calibration using the xinput interfaces. yes, the original DESCRIPTION spells it with an extra o β xlibinout_calibrator(8) β not me preserving the lore, but also literally me preserving the lore π
The possible outcomes of this command are: set a new X11 configuration; create a new configuration file for X11; show the xinput command option to set the new matrix calibration. three outcomes, three vibes β¨
π OPTIONS π
--output-file-x11-config=<filename>β sets the filename where the X11 configuration will be saved. Implies--show-x11-config.--output-file-xinput-cmd=<filename>β sets the filename where the xinput command will be saved. Implies--show-xinput-cmd.--threshold-misclick=<nn>β sets the threshold for accepting or rejecting a click. The four clicks have to be in the corners of a rectangle. The value you pass is the maximum allowable distance between the click and the ideal point. If the value is0(the default), the check is not performed.--threshold-doubleclick=<nn>β sets the threshold for accepting or rejecting a click. It sets the minimum distance between clicks to accept them. If the value is0, the check is not performed. Default value1.--device-name=<devname>|--device-id=<device-id>βxlibinput_calibrator(8)selects the device to operate on automatically. If for some reason that's not possible (multiple devices are available, for example), you can explicitly select the device with--device-id=...or--device-name=.... the former takes precedence.--matrix-name=<matrix-name>β sets the name of the matrix used for the calibration.--show-x11-configβ shows theX11file configuration with the newmatrix_calibration.--display=<display>β sets the X11 display.--show-xinput-cmdβ shows thexinput(1)command for thematrix_calibration.--show-matrixβ shows the final matrix when the program ends.--verboseβ be verbose.--dont-saveβ don't save the setting in X11 when the program ends.--matrix=<x1,x2..x9>β sets the initial matrix before doing the calibration. By default,xlibinput_calibrator(8)sets the calibration matrix to the identity (i.e. all1in the diagonal). With this option it's possible to set another matrix. Note that if something goes wrong or the calibration fails, the original matrix is set in X11. iykyk, that's your safety net π«Ά--monitor-number=<nr>β sets the monitor to display the window. If<nr>is equal toall, the window will span all the monitors area. Usexrandr --listmonitorsto get the<nr>associated to the monitor.--list-devicesβ shows all the available devices with their ID.
π AUTHOR π
Goffredo Baroncelli <kreijack@inwind.it> β the icon behind the icon π
okay that's the whole page, bestie. this cutie comes from the xlibinput_calibrator(8) manual (that's the source, fr fr), dated 01 January 1980 πβ¨ periodt.
π¦ where this page comes from
- nixos 26.05: xlibinput-calibrator 0.11
- nixpkgs unstable: xlibinput-calibrator 0.11
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms