-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add package for keyd #744
base: testing
Are you sure you want to change the base?
Add package for keyd #744
Conversation
Co-authored-by: Nathaniel van Diepen <Eeems@users.noreply.github.com>
I'll have to give this a test on my rM1 to make sure it works as expected. I assume you've tested the latest changes on your rM2 to make sure it works as expected? |
Yep, all the keys appear to remap properly. Testing tips:
|
Do you know what version the uinput module was enabled from? Should a version check be added to the package script? |
Not offhand, it was one of the earlier 3.x versions I believe. At this point, we will have to hold off on merging this until 3.x support is in progress. |
I just want to note that, when I installed the ipk from the build artifact, in the So either we add a symlink, or try and fix this(which shouldn't happen considering it was supposed to be /opt/bin/keyd) |
No we wouldn't want to have it be in /usr/bin. That's very odd that the file provided isn't being used. My guess is that the keyd source has its own copy of the service file that is replacing the one included in this repo. |
Yup, so I thought, why not copy over keyd.service later in the package code instead of at the very beginning(So maybe put it in a temp folder first) |
I haven't looked too closely, but if there is a keyd.service file in the source that's overwriting the one included in the package folder, changing the order you install the files from the source directory wont do anything. The file isn't there to copy, because it's been replaced. The file will need to be renamed in this repo, and then renamed as part of package() when it's installing it to the final location in the package. Ideally the toltec build system (and toltecmk) should be updated to detect this kind of thing and error if there are files that are going to be clobbered. |
Checking for clobbered files it is probably hard: in this particular instance there is no overlapping in the sources, the problem arises at compiel time: https://github.com/rvaiya/keyd/blob/master/Makefile#L37 |
In this particular case having a separate keyd.service is not needed: it suffices to add |
A tiny bit more than that was required to do it properly, but it should be working now. |
This is still not working: the binary is |
It does not, which is why I added the sed line. I forgot that the default prefix is /usr. The latest code does, but we are dealing with the v2.4.3 tag which is missing some build process fixes. |
This is annoying |
It is 😆 , the next time they push a release it will no longer be an issue. |
For future reference when we get here, I think this is a good/sane default for the US layout. It at least makes the legends match what the keyboard actually outputs, and exposes some needed keys for terminal usage.
Xochitl doesn't seem completely happy with allowing +/= on the 0/- keys though. |
Keyd seems to freak out on boot and has key-repeats even when the key is clicked once.. I have to restart the service to fix it |
I haven't experienced this. What settings are you using? |
That’s my config fire |
Have you checked the keyd logs to see if it has anything useful? It works by grabbing all other physical keyboard input and creating it's own evdev device with uinput to emit events from. uinput handles automatically emitting the key repeat events. Because of this, keyd might just have missed the event that the key was released. |
For the scandinavian keyboard (and others that need non-ascii input keys), one would need xkbmap to make the compose-hack work. |
I've tested a2ab078 (build 9670591399) on an rm2 at Upon installation, it instructed me to disable the shutdown target, which seems not relevant.
I was able to set the `dvorak` layout with the following config file
Having set the dvorak layout, the shortcuts in #744 (comment) do not work correctly. I'll post a full config later that makes those all work as expected. |
What launcher are you using? And what is the output of
If you have a configuration to change the layout to dvorak, it would conflict with the settings I provided. I would recommend reviewing the keyd logs to see if it complains about anything ( |
Nothing beyond the usual startup messages.
Yes, I'll do that and post it. |
Everything looks fine here, so it would be just that the two configurations are compatible with each other, as one overrides the other. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since uinput isn't available on OS 2, this will need to be limited to the rmallos3 architecture, so it's only available on 3.x.
It would probably be worth sorting out how we intend on other packages providing configuration for keyd, but that is probably better served by the first package who does.
here is my dvorak keyd config, along with an image of the keyboard with the symbols overlaid |
This PR adds
keyd
, a tool for remapping keys. It has been tested on an rM2.No configuration is currently bundled. My intent is to create a separate
keyd-configs
package with community configs (and possibly a mechanism to automatically apply the right one for the active keymap).