XINPUT TEST TERMINAL INSTALL
XINPUT TEST TERMINAL SERIAL

Shift, Ctrl, Alt) at the same time.īutton4 and Button5 are typically the Mousewheel. The None part in the first column means Mouse button klicks are registered without holding any modifier keys (e.g. You can use xprop WM_CLASS | grep -o ''*'' | head -n 1 and then click a windows, to get the Name which should be in the config. If you want to use that config only in chrome, for example, you could insert there '^google-chrome$'. Where the '.*' means, use that config for all x-windows. imwheelrc like this: cat >~/.imwheelrc< xinput test terminal

Kill all xbindkeys processes: killall xbindkeys Replace b:6 and b:7 with your numbers of xev output. 'xte 'keydown Alt_L' 'keydown Right' 'keyup Right' 'keyup Alt_L'' Root 0x233, subw 0x0, time 9223854, (94,21), root:(1774,85),Įdit your xbindkeys configuration, e.g.: nano ~/.xbindkeysrcĪnd add the lines below 'xte 'keydown Alt_L' 'keydown Left' 'keyup Left' 'keyup Alt_L''

XINPUT TEST TERMINAL SERIAL

In my case, note the output button 6 and button 7: ButtonRelease event, serial 36, synthetic NO, window 0x2e00001,

XINPUT TEST TERMINAL INSTALL

Install the package x11-utils, we need the command xev: sudo apt-get install x11-utilsĬheck the code for the two mouse buttons. One of them is an external USB-C one and the other one is a built-in PCI (or i☬?) one.Install the package xautomation, we need the command xte: sudo apt-get install xautomation

(I ran these commands on a system with two touch screens. Or to get the name(s) of the touch screen(s): $ udevadm info -export-db | awk '/ID_INPUT_TOUCHSCREEN=1/' RS= | grep '^E: NAME=' | cut -d ''' -f2 To build upon Sylvain Pineau's answer: Using awk instead of grep you can get all information of the block(s) the ID_INPUT_TOUCHSCREEN=1 was found in. The command to use is finally: udevadm info -export-db | grep ID_INPUT_TOUCHSCREEN=1 Keyboards have this, but also things like lid switches which have just a few buttons Touchscreens and tables have this flag as well, since by the type of events they can produce they act as a mouse. Udev already classifies the input devices (See ), the supported flags are:

Xinput test terminal