Skip to content

Commit

Permalink
Readme: Minor wording clarifications
Browse files Browse the repository at this point in the history
  • Loading branch information
anko committed Oct 1, 2021
1 parent 84acdd8 commit 7e38d0a
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions readme.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,15 @@

Simple X11 keylogger.

- Simple output format: one line on `stdout` per key event.
- Simple to audit: Short single file of modern C.
- Simple output format: One line on `stdout` per key event.
- Simple to audit: One short file of modern C.
- Simple to run: Does not need `sudo`.

## Examples

### Keypresses only

Given no flags, `xkbcat` prints only keypresses, one per line. Here's the
Given no options, `xkbcat` prints only keypresses, one per line. Here's the
output when I type "Hi":

Shift_L
Expand Down Expand Up @@ -39,7 +39,7 @@ package.

## Usage

Flags you can pass (all optional):
Options you can pass (all optional):

- `-display <display>`: set target X display (default `:0`)
- `-up`: also prepend key-ups (default: don't)
Expand Down Expand Up @@ -69,9 +69,9 @@ Then just use your computer as usual. Interrupt signal (`C-c`) to quit.

### Programs for logging other X11 events

- [xinput][6] invoked as `xinput --test-xi2 --root` logs everything; even
mouse movements and clicks, and touchpad stuff. Its output is very
comprehensive, but harder to parse.
- [xinput][6] invoked as `xinput --test-xi2 --root` logs everything
input-related; even mouse movements and clicks, and touchpad stuff. Its
output is very comprehensive, but harder to parse.

- If you need to log X11 events more generally, various protocol monitoring
programs are listed in the [X11 debugging guide][7].
Expand Down

0 comments on commit 7e38d0a

Please sign in to comment.