How do you use it? about interception-k2k HOT 8 CLOSED

Thank you, I managed to tweak it to my needs.

from interception-k2k.

Sorry for the noise, it seems that the interception program itself is segfaulting. I'll open an issue there.

It would be great to have installation instructions nevertheless.

from interception-k2k.

Thanks for your feedback, added example udevmon.yaml config to readme.

If you managed to solve that bug and you have some trouble with my plugin don't hesitate to write me.

Two notes about your (segfault) bug report:

• It should be submitted to Interception tools instead of caps2esc.
• Provides no valuable info other than the fact that there is a bug somewhere. You should try running gdb (search for "cmake gdb") to find out where it happened.

from interception-k2k.

Thanks, I learned a lot, in particular that I should have recompiled interception-tools and not just caps-2-esc.

I have additional questions regarding your plugin:

• doing double shift does not seem to be setting caps-lock. What happens is that shift is ignored.
• space + something else is translated to super_l + something else. Is this on purpose?

from interception-k2k.

doing double shift does not seem to be setting caps-lock. What happens is that shift is ignored.

For me it also not changing CapsLock led, but it works as expected (check evtest to see it really sends CapsLock key). I doubt a little that it doesn't work for you, but if really doesn't I fear I cannot do anything to make it work (at least it's not an issue with interception-k2k).

Are you using mechanical keyboard? Maybe that could be an issue.

space + something else is translated to super_l + something else. Is this on purpose?

Absolutely! Space bar is a long-long key that just consumes too much valuable space on the keyboard and you can even conveniently reach it by both hands. What a waste! I'm using tiling WM, so I use Super keys a lot (moving among windows/workspaces) and spacebar is the best choice:

• I can reach it by both hands, while I can hit some keys quickly with my another hand.
• I don't have to twist out my hands to press Super keys.

It's configured here, by the way:

You can read it as follows: If you want to get a space you have to be fast because it translated to super_l as soon as keyboard sends the first key repeat signal.

from interception-k2k.

Sorry for the noise, it seems that the interception program itself is segfaulting. I'll open an issue there.

Hmm. I wanted to test a configuration for you so I restarted udevmon to assure that it surely works. It was a mistake. I also get segfaults. At first, I thought it's because my low quality plugin :), but hopefully not:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7f34f50 in YAML::detail::node_data::begin() ()
   from /usr/lib/libyaml-cpp.so.0.6

As a sidenote: Yes, yaml-cpp get updated. Hurrray!

Have you managed to overcome this issue?

from interception-k2k.

I had the same issue, and I did a rebuild of interception-tools (I think it must be linked again, or some interface has changed). I'm using yay so I asked for a clean rebuild.

For my double-shift issue, I see that it actually changes the shift to control. I suspect I might have some remnants of a "switch caps-lock and control" somewhere that might do that.

Regarding the general configuration, where can I find the names of keys? I would like to write my own translation. And is it possible to have different translations for different physical keyboards?

from interception-k2k.

where can I find the names of keys?

Great question! Here: /usr/include/linux/input-event-codes.h.

And is it possible to have different translations for different physical keyboards?

It's out of scope of an interception plugin. You should look around at udevmon and its yaml config. As I remember you can match for different input devices, so this way you can make different "translation pipes" for different inputs.

from interception-k2k.