logkeys

logkeys copied to clipboard

Actually parse keycodes instead of assuming they're all present in order

1

Some keyboards weren't being mapped correctly. It was due to parsing `dumpkeys` incorrectly Fixes the other half of #162 and #245, along with PR https://github.com/kernc/logkeys/pull/246

za3k

Fix overflow

2

I believe this fixes issue #239, where args.flags was getting clobbered by an overflow The problem was that sizeof(char_or_func) is 129, not 128, due to the trailing null byte. However,...

za3k

Make -u option work

2

Fixes #245 -u worked only together with --export-keymap. Now it also works for normal logging operation.

za3k

Keymapping issue

1

It looks like something odd is going on with keymaps. On two computers, I run: sudo logkeys -s -u --no-daemon I add keycode logging by adding a printf in `update_key_state`...

za3k

Fix #122

za3k

Removes the `Logging started...` and `Logging stopped at 2022-08-03 20:06:36+0100` messages. Indepdendent of `--no-timestamps`. Closes #240 Open to suggestions on a better option name if you have one.

za3k

Most Keys Log Accurately - Some Keys Are Broken! :/

9

Hi Folks. If I placed this request in the wrong area, my apologies. Please re-direct to the right area if necessary. I borrowed one of the earlier posts as a...

ultrablast

`--no-timestamps` not working

1

``` $ sudo logkeys -s --no-timestamps $ sudo tail -f /var/log/logkeys.log Logging started ... 2022-08-03 20:11:45+0100 > fwjji 2022-08-03 20:11:55+0100 > ``` Edit: Tested using 0.2.0

za3k

[Feature Request] Suppress logging start/stop messages

1

I'd love to suppress `Logging started ...` and `Logging stopped at 2022-08-03 20:06:36+0100` as well as timestamps.

za3k

Not working in Ubuntu 20.04 + i3

4

The title pretty much sums it up, nothing logged. Command run: `sudo logkeys --start --output test.log` System: Ubuntu 20.04, WM: i3-gaps

Rizhiy