News for hackers. Stuff that matters.

nejdetckenobi

Show HN: Hot Macropad – a user-level Linux macropad daemon using evdev and Bash

https://github.com/nejdetckenobi/hot_macropad

Hi HN,I built Hot Macropad, a small user-level daemon for Linux that lets you bind scripts to keys on a macropad (or any input device exposed via evdev).Key points:Written in Bash, minimal dependenciesUses evtest to listen to evdev eventsOne script per key (KEY_A.sh, etc.)Supports “pages” (key layers) and page switching from scriptsRuns as a systemd user service (no root daemon)Designed to work...

( Read More... | no comments | on HN )
Re:Microsoft and GitHub have held acquisition talks on Saturday June 02, 2018 @08:09AM (#17214192)
They're literally ruining my life. First Minecraft, now GitHub? Congratz MS. Now I hate you more.
Re:Ngrok: Secure tunnels to localhost on Saturday May 06, 2017 @04:40AM (#14279348)
long time ngrok user here. used several times to show my prototypes to the others. It's simpler than deploying on heroku (or anywhere actually), and is without restrictions ofc because you use your own hw.
Re:Announcing Pipenv on Monday January 23, 2017 @02:03AM (#13460405)
normally I use virtualenvwrapper and that makes a virtualenv directory for all virtualenvs you create with it. before that, I always create my projects' venvs inside my project hierarchy.

I had a dilemma about it. But after all, you can not move your venv directory unless you use `--relocatable` option. So, anyone have a strong argument about creating venvs inside your project directory?