Console gets cluttered when PyKeyboardEvent._tap doesn't recognize keycodes pressed
See original GitHub issueI keep getting messages like :
Unable to determine character.
Keycode: 65 KeySym 0
in my console, each time I press Shift+Space (not that I mean to, it just happens and clutters the console).
It also happens when I press Ctrl+Shift+Tab, which I do mean to press (Keycode 23 KeySym 65056) and C+S+ left and right arrows (Keycode 113/114 Keysym 0), among others.
As a new user, it makes me think keypresses are listened to, which I didn’t see advertised and feels slightly worrying. I can only hope it is not logged in order, at most in aggregated form. I mean, I type passwords sometimes, and very much want that signal to be forgotten on the spot by all watchers. Even in aggregated form, I’m not sure I want to store statistics about how my typing contains many more %, &, and w than otherwise usual, or how some days all I type are the letters “adoprssw”. Very less all individual events with high-precision timing, which is what the docs seems to indicate.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (12 by maintainers)

Top Related StackOverflow Question
@nikanar: Regarding manual logging: I’m interested in that as well, but I’m a bit apprehensive about expanding the scope of ActivityWatch to include it at this point in development. It would be rather easy to write a ActivityWatch client that stores the data in the ActivityWatch datastore. That way you could leverage some of the visualization work we are doing. I do manual logging right now with a simple textfile (using Standard Notes), works well for me across all devices but lacks any visualization.
It’s certainly something I’d want to add to the web UI (RescueTime-style), but right now it’s not a priority. If you have any ideas, feel free to create an issue.
Regarding programmatical export: Check out the aw-client library, it makes fetching events easy from Python. Not very well documented right now, but the code should be pretty clear.
This was finally fixed in https://github.com/ActivityWatch/aw-watcher-afk/commit/cb7587e70cd2394b8a463ac906811bc711e4c12b.