diff options
| author | 2016-05-16 13:30:47 +0100 | |
|---|---|---|
| committer | 2016-05-16 13:30:47 +0100 | |
| commit | f28389fb721664046f67d400676ad203dabad2fa (patch) | |
| tree | 35248f7e7d6a45bf049e2375aa785f73f847102b | |
| parent | c61ccdc25daac24b4479b1851550d93c13e86fd5 (diff) | |
| download | xkbcat-f28389fb721664046f67d400676ad203dabad2fa.tar.gz xkbcat-f28389fb721664046f67d400676ad203dabad2fa.zip | |
Readme: clarify other recommendations' wording
| -rw-r--r-- | readme.markdown | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/readme.markdown b/readme.markdown index 1895b29..9df25f1 100644 --- a/readme.markdown +++ b/readme.markdown @@ -53,9 +53,9 @@ If you need to log keys across a whole Linux system (also in the framebuffer—not just in X11), try [keysniffer][1]. It works via a kernel module, and needs `sudo`. -If you want to see what characters the user actually typed, [`xspy`][2] or -[`logkeys`][3] might be better for you. They support keymaps and have logic for -resolving keys pressed together with modifier keys into the actual typed text. +If you want to see what characters the user actually typed (with modifier keys, +backspace, etc resolved into text), [`xspy`][2] or [`logkeys`][3] might be +better for you. If you want to add timestamps to each line for logging purposes, I recommend piping to the [moreutils package][4]'s `ts`. [These answers][5] feature |
