Hacker News Reader

Comment by diggan | Hacker News Reader

I think the GIF is supposed to give the breakdown. As I understand, type "@mymacro" and it can expand it to whatever you define.

Wouldn't hurt to have a description in text though...

View on HN

I do realise it now that it's missing it's usage. It's a simple keyboard macro which supports all printable characters for triggers and everything for expansions. It sends native key presses if all the expansion are printable characters. If not, it uses clipboard and sends `Ctrl+V`

I'm used to user-facing macros (as opposed to say a Lisp macro) being scripts triggered by a keyboard shortcut, so the terminology was confusing to me. Calling this "text expansion" or "text substitution" would have made immediate sense.

Thanks! I think maybe not everyone understands exactly what a "keyboard macro" is, that you type something and it fills out predefined text. At least judging by some comments here :)

I think more people know what a keylogger is and are confused by that.

It's mysterious to me as well, but yeah after looking through the code briefly I think you define macros in the keydoggerrc file, and then keydogger watches the clipboard for triggers and responds accordingly. I love the idea, still a bit too much in the dark on the implementation to have an opinion though. Given the highly sensitive nature of the clipboard, I appreciate how small the app is because it's auditable.

OP: Cool project, thanks for sharing!

You get it perfectly. Being auditable was one of the priority which is exactly why it's small.

Regarding the clipboard, it's a third party dependency. I looked into implementing Wayland clipboard myself but it is too deep Wayland. The only reason clipboard exists is because I cannot send non-printable characters using uinput.

Reply on news.ycombinator.com