PKGBUILD for Archlinux

[m040601]

First of all thank you for this tool.

I just by mere luck bumped into it after a long search for similar tools. Tools that work in the Linux Console (not only X11). Examples like, Triggerhappy, hkd (alemani.eu), kmonad , see my odissey here, https://aur.archlinux.org/packages/hkd-git.

As soon as I saw "suckless", "config.h", and a clean understandble README (for end users, not linux input/evdev or C coders experts) I knew it was my lucky day.

... See [linux/input-event-codes.h]
(https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h) for a list of available key codes ...

This is the kind of simple sentence, that doesnt cost much to write in a README, and makes life so easier for end users. Instead of wasting time on the Internet, reading things meant for developers.

I'm on Archlinux. I'm not a developer, just a competent command line end user. Framebuffer and console fanatic. Tested immediately and works like a charm.

• Question 1: Do you, yourself, use it daily ? Plan on maintaining it long term ?

This kind of tool is also interesting in small devices, with a small keyboard or just a simple numeric keypad attached per usb.

• Question 2: Since it's C coded it will probably compile everywhere right ?

I'm gonna test it in ARM (Raspberry Pi Archlinux, armv7h etc). Should work also, and I'll report back.

A big dream would be if it would compile in MIPS architecture, for a small router (with an USB port). If it could some day make it into Openwrt, as an official repo package. That wouldextremely usefull for running custom actions assigned to keyboard events, https://openwrt.org/docs/guide-user/hardware/hardware.button .

All these are information that you might want to hint to in the README.

I noticed you seem to be also and Archlinux user. But there isnt' a PKGBUILD for this tool.

• Question 3: Could you please provide one, and publish it on the right place, the AUR system.

The PKGBUILD would probably also need to:

• add a systemd wide service ?
• include the README, example "config.h" and eventually other docs to install in /usr/share/doc/hkd-aaron
• make sure to use "arch=('x86_64' 'armv7h')" or even better "arch=('any')"

Thanks in advance.

PS: I have, as an end user, other questions, but I'll writed detailed about it in another post. Maybe as suggestions for the README or some OVERVIEW docs, ex:,

This whole "bazaar" "rocket science" linux input system, evdev, console v. X11, "hotkeys" is not the friendliest terrain for us end users to get a clean overview.

I've avoided diving into "interception tools" till know, because although it seems well maintained and actively developed, it lacks a clean straight forward README or OVERVIEW. For end users, not the ones programming it. I have difficulties "fitting" it into my head.

[aaronamk]

I am so sorry I missed this until now! I just happened to check back on the repo and saw this wonderful feedback.

I just by mere luck bumped into it after a long search for similar tools.
As soon as I saw "suckless", "config.h", and a clean understandble README (for end users, not linux input/evdev or C coders experts) I knew it was my lucky day.

... See [linux/input-event-codes.h]
(https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h) for a list of available key codes ...

This is the kind of simple sentence, that doesnt cost much to write in a README, and makes life so easier for end users. Instead of wasting time on the Internet, reading things meant for developers.

I'm on Archlinux. I'm not a developer, just a competent command line end user. Framebuffer and console fanatic. Tested immediately and works like a charm.

This was amazing to read. Someone found my tool independently, used it, and it worked.... What a feeling.

* Question 1: Do you, yourself, use it daily ? Plan on maintaining it long term ?

I still do use this on my main PC. I haven't had to maintain it at all for a while, but if I run into a bug and fix it, I will merge the changes here.

* Question 2: Since it's C coded it will probably compile everywhere right ?

I hope so, let me know if it doesn't.

A big dream would be if it would compile in MIPS architecture, for a small router (with an USB port). If it could some day make it into Openwrt, as an official repo package. That wouldextremely usefull for running custom actions assigned to keyboard events, https://openwrt.org/docs/guide-user/hardware/hardware.button .

All these are information that you might want to hint to in the README.

I noticed you seem to be also and Archlinux user. But there isnt' a PKGBUILD for this tool.

* Question 3: Could you please provide one, and publish it on the right place, the  AUR system.

I am an Arch user, but I have no experience creating pkgbuilds or adding things to the AUR. Given that this is a suckless-style program which requires edits to the source code for configuration, I hadn't planned on adding something like this. I think my first priority if I were to put significant further work into this project would be to add useful features, but I am not against the AUR idea if someone else (you seem to be knowledgeable?) wanted to do this.

PS: I have, as an end user, other questions, but I'll writed detailed about it in another post. Maybe as suggestions for the README or some OVERVIEW docs, ex:,

Hit me

This whole "bazaar" "rocket science" linux input system, evdev, console v. X11, "hotkeys" is not the friendliest terrain for us end users to get a clean overview.

Yes.

I've avoided diving into "interception tools" till know, because although it seems well maintained and actively developed, it lacks a clean straight forward README or OVERVIEW. For end users, not the ones programming it. I have difficulties "fitting" it into my head.

I'm with you on the user friendliness of interception tools. That's why I put in some effort removing hkd's dependency on that library. Let me know if you have questions about interception tools though and I might have an answer.

Edit: I had no idea there was another project of the same name... does this mean I fight this Mauri guy to the death?