summaryrefslogtreecommitdiff
path: root/Evemu.mdwn
diff options
context:
space:
mode:
authorPeterHutterer <PeterHutterer@web>2013-07-23 16:57:33 -0700
committerwww <iki-www@freedesktop.org>2013-07-23 16:57:33 -0700
commit6be716f65ddd1b44909b624428392be3bc4b3fc8 (patch)
treef19f32b6e88d7a731aba071adac2fed1e2380e8e /Evemu.mdwn
parente5073f8c7f52a79073988544d6f16a5b0d409854 (diff)
s/evtest/evemu
Diffstat (limited to 'Evemu.mdwn')
-rw-r--r--Evemu.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/Evemu.mdwn b/Evemu.mdwn
index 9d1a185e..1acb4f4e 100644
--- a/Evemu.mdwn
+++ b/Evemu.mdwn
@@ -37,7 +37,7 @@ As of evemu 1.1.0, you only need to run evemu-describe if you're not planning to
## Grabbed devices
-evemu-record cannot see events while another process has an EVIOCGRAB on the device. This is the case for the X.Org synaptics and wacom drivers, you must disable the devices or VT-switch away before running evtest to see events. Devices can be disabled with
+evemu-record cannot see events while another process has an EVIOCGRAB on the device. This is the case for the X.Org synaptics and wacom drivers, you must disable the devices or VT-switch away before running evemu to see events. Devices can be disabled with
xinput set-prop "my device name" "Device Enabled" 0
If you need the device enabled to verify that the bug is indeed triggered, use the following xorg.conf.d snippet: