diff options
| author | 2016-03-05 02:31:14 +0000 | |
|---|---|---|
| committer | 2016-03-05 02:31:14 +0000 | |
| commit | 1a5e733cb27143215f5ce19ef8ce8ff4cb3035fe (patch) | |
| tree | 5bdb2a48976deba65fabf5582fb2da3c3b846c96 | |
| parent | 4d1e09c91e3b1d5d5655f61d78934bfb5db7504f (diff) | |
| download | xkbcat-1a5e733cb27143215f5ce19ef8ce8ff4cb3035fe.tar.gz xkbcat-1a5e733cb27143215f5ce19ef8ce8ff4cb3035fe.zip | |
Clearer wording on how related programs differ
| -rw-r--r-- | readme.markdown | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/readme.markdown b/readme.markdown index 0f31192..fa9cb58 100644 --- a/readme.markdown +++ b/readme.markdown @@ -50,9 +50,9 @@ Then just type as you would usually. Interrupt signal (`C-c`) to end. ## Related programs -If you like spying on people (ethically, of course), [`xspy`][1] or -[`logkeys`][2] might be better for you. They use the modifier keys to infer -what was actually typed, so it's easier to read what's happening. +If you want to see what characters the user actually typed, [`xspy`][1] or +[`logkeys`][2] 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 add timestamps to each line for logging purposes, I recommend piping to the [moreutils package][3]'s `ts`. [These answers][4] feature |
